Skip to main content
MediumHeadersOWASP A05:2021CWE-942

How to fix: Wildcard CORS Policy

The Access-Control-Allow-Origin header is set to '*', allowing any origin to make cross-origin requests.

Why it matters

Any website can make requests to your API, potentially stealing sensitive data.

CORS controls which external domains can access your API. A wildcard '*' means any website can make requests.

How to fix it

  1. 1Replace the wildcard with specific trusted origins.
  2. 2Validate the Origin header against an allowlist.
  3. 3Never combine * with Allow-Credentials: true.

Code examples

Next.js CORS

TypeScript
const ALLOWED = ['https://yourdomain.com'];
const origin = request.headers.get('origin');
if (ALLOWED.includes(origin)) {
  headers['Access-Control-Allow-Origin'] = origin;
}

Nginx

nginx
set $cors_origin '';
if ($http_origin ~* '^https://(www\.)?yourdomain\.com$') {
    set $cors_origin $http_origin;
}
add_header Access-Control-Allow-Origin $cors_origin always;

Apache

APACHE
SetEnvIf Origin "^https://(www\.)?yourdomain\.com$" CORS_ORIGIN=$0
Header always set Access-Control-Allow-Origin "%{CORS_ORIGIN}e" env=CORS_ORIGIN

Express (Node.js)

JavaScript
import cors from 'cors';
app.use(cors({
  origin: ['https://yourdomain.com'],
  credentials: true,
}));

Deno (Hono)

TypeScript
import { cors } from 'hono/cors';
app.use('*', cors({
  origin: ['https://yourdomain.com'],
  credentials: true,
}));

Bun (Elysia)

TypeScript
import { cors } from '@elysiajs/cors';
app.use(cors({
  origin: ['https://yourdomain.com'],
  credentials: true,
}));

References

Detected automatically by VulnRadar. The check id is cors-wildcard, stable across every scan so you can filter or diff on it.

See every headers check

Questions

How severe is Wildcard CORS Policy?
VulnRadar rates this medium severity in the headers category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id cors-wildcard, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Wildcard CORS Policy map to?
It maps to CWE-942. In the OWASP Top 10 it falls under A05:2021.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for wildcard cors policy

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

How to fix: Wildcard CORS Policy | VulnRadar