Skip to content

The problem list is free. A fix prompt for each one is $9.

See pricing

Base44

Open CORS on a Base44 app

Base44 hosts the app it builds. The hosted URL is the thing to paste. Public files and headers on that host are in scope.

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.

Base44 project settings and databases are not opened. The scan does not log in as a user of the app.

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 Base44 project?

No. Base44 project settings and databases are not opened. The scan does not log in as a user of the app.

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.

Free public scan