v0
Auth misconfiguration on a v0 app
v0 generates UI you then deploy, often on Vercel. The scan starts at the deployed URL. It sees the shipped page, not the v0 chat that produced the components.
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.
A component that was generated but never deployed is not part of the check.
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 v0 project?
No. A component that was generated but never deployed is not part of the check.
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.