VibeSec
All capabilities
High (7.5)Serious risk

CORS Misconfiguration

A05:2025Passive checkCVSS 7.5

High impact. If this is found on your site, treat it as urgent. It can lead to real damage and is worth fixing before anything else.

What it is

Origin reflection or wildcard with credentials, letting any site read authenticated responses on a victim's behalf.

How attackers abuse it

A secret (API key, token, password) is exposed in your front-end code or responses. Anyone can read it and use it as you: charge cards, drain an AI budget, or read your database.

Attacker playbook

  1. 1Open the site's public JavaScript and search for key patterns and high-entropy strings.
  2. 2Pull out any secret key found in the client code.
  3. 3Use it directly against the provider's API, on your account.

How VibeSec detects and confirms it

VibeSec checks for this with a passive, read-only scan that is safe to run on any site. We use VibeSec native and base the finding only on what your site already exposes publicly.

VibeSec native

If this is in your report: how to fix it

  • Rotate the exposed secret immediately and assume it is compromised.
  • Move secrets to server-side environment variables; never ship them to the browser.
  • Call third-party APIs from your server, and re-scan to confirm the key is gone.

Check your site for this

Run a scan and see whether this affects you, in plain language with copy-paste fixes.

Scan your site for free