Edit the main.js file and add your link you want to test. Open index.html in browser then open inspect -> console, if its vulnerable you can see data being fetched.
If another domain is allowed by the policy, then that domain can potentially attack users of the application. If a user is logged in to the application, and visits a domain allowed by the policy, then any malicious content running on that domain can potentially retrieve content from the application, and sometimes carry out actions within the security context of the logged in user.
Even if an allowed domain is not overtly malicious in itself, security vulnerabilities within that domain could potentially be leveraged by an attacker to exploit the trust relationship and attack the application that allows access. CORS policies on pages containing sensitive information should be reviewed to determine whether it is appropriate for the application to trust both the intentions and security posture of any domains granted access.
To test same in burpsuite just add below header in request
origin: https://evil.comIn response if you get this header with your mentioned domain in request (in this case https://evil.com), then it's vulnerable to CORS
Access-Control-Allow-Origin: https://evil.com