v0
Open CORS on a v0 app
v0 generates UI you then deploy, often on Vercel. The scan starts at the deployed URL. It sees the shipped page, not the v0 chat that produced the components.
A wildcard Access-Control-Allow-Origin on the public response.
What the scan can see
Access-Control-Allow-Origin: * is a medium finding. The same wildcard with Access-Control-Allow-Credentials: true is higher. Browsers reject that pair, but it shows the config is confused.
What it does not do
CORS on an API host you did not paste is not checked. The scan does not send a credentialed browser request to prove data leaks.
A component that was generated but never deployed is not part of the check.
What to do next
Remove the wildcard from a page that does not need it. On an API, list the exact origins you own. Do not copy the request Origin into the response without checking it.
Questions
Does this open my v0 project?
No. A component that was generated but never deployed is not part of the check.
Can the scan prove open cors is fully fixed?
CORS on an API host you did not paste is not checked. The scan does not send a credentialed browser request to prove data leaks.
What should I do if the scan finds it?
Remove the wildcard from a page that does not need it. On an API, list the exact origins you own. Do not copy the request Origin into the response without checking it.
Scan a URL you own
The same free check as the homepage. You confirm the app is yours before it runs.