Replit
Open CORS on a Replit app
A Replit deployment is an ordinary website. The page, its same-origin scripts, and the headers from that host are what a visitor receives, and what this scan reads.
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.
The Replit API, the workspace, and secrets that exist only in Replit's server environment are outside the fetch.
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 Replit project?
No. The Replit API, the workspace, and secrets that exist only in Replit's server environment are outside the fetch.
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.