Base44
Auth misconfiguration 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.
The public clues this scan can see, not a login test.
What the scan can see
Cookie flags (Secure, HttpOnly, SameSite) when a cookie is set, wildcard CORS, and secrets in the client bundle. A service_role key or a session secret in JavaScript is an auth problem because anyone who loads the page can copy it.
What it does not do
The scan does not try passwords, bypass a login, reuse a session, or call your auth provider. It cannot tell you that a rule allows the wrong user.
Base44 project settings and databases are not opened. The scan does not log in as a user of the app.
What to do next
Keep session cookies HttpOnly and Secure. Keep privileged keys on the server. Review who your auth rules allow, in the provider's console, because this scan will not do that review.
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 auth misconfiguration is fully fixed?
The scan does not try passwords, bypass a login, reuse a session, or call your auth provider. It cannot tell you that a rule allows the wrong user.
What should I do if the scan finds it?
Keep session cookies HttpOnly and Secure. Keep privileged keys on the server. Review who your auth rules allow, in the provider's console, because this scan will not do that review.
Scan a URL you own
The same free check as the homepage. You confirm the app is yours before it runs.