> I've been reading in the last couple of days about CORS and in a lot
> of places it's mentioned as it is a "Security" feature to help the
> world from cross domain forgery.

You either misunderstood the benifits of CORS or may be you have read that in some *amateur* blogs done by developers who are more worried about *how to make it work* than *how to make it safe* (if you understand what I mean), because CORS rather makes your web application vulnerable to such attacks ([CSRF][1]) when you open  cross-origin requests from the attacker's  origin by using CORS with the following header: `Access-Control-Allow-Origin: *`



> How is CORS helping and what's the benefit of it?

CORS was born to lighten the restrictions of the [SOP][2] for **trusted** requests *only*. But the problems start exactly with that *trust*. An attacker could do harm through the [origins][3] by forging malicious requests through GET and POST methods for example, and  may expose you even [DNS rebinding][4]


  [1]: https://www.owasp.org/index.php/CSRF
  [2]: https://tools.ietf.org/html/rfc6454
  [3]: https://www.rfc-editor.org/rfc/rfc6454#section-4
  [4]: https://en.wikipedia.org/wiki/DNS_rebinding