Replit
Auth misconfiguration 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.
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.
The Replit API, the workspace, and secrets that exist only in Replit's server environment are outside the fetch.
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 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 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.