Bolt
Open CORS on a Bolt app
Bolt serves a live preview from the project you are editing. That preview is a public address. Code that looks private in the editor is still in the script the preview downloads.
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 scan does not sign into Bolt or read the editor. It only requests the URL you paste and a short, fixed list of paths on that host.
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 Bolt project?
No. The scan does not sign into Bolt or read the editor. It only requests the URL you paste and a short, fixed list of paths on that host.
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.