Medium severityJavaScript / TypeScriptInsecure ConfigurationMEDIUM confidence
CORS Acao Wildcard Header
An Access-Control-Allow-Origin:* header is set manually, allowing any origin to read responses.
Standards mapping
- OWASP Top 10
- A05:2021 - Security Misconfiguration
- OWASP ASVS
- V14.5.3 (L1)
Vulnerable vs. safe
Flagged by this check
res.setHeader("Access-Control-Allow-Origin", "*");Passes - the safe pattern
res.setHeader("Access-Control-Allow-Origin", "https://trusted.example.com");Why it matters & how to fix it
An Access-Control-Allow-Origin:* header is set manually, allowing any origin to read responses. Emit a specific validated origin rather than a wildcard.
References
Rule ID integsec-js-cors-acao-wildcard-header - engine: Opengrep - license: MIT - Copyright (c) IntegSec Inc.
TurboPentest runs this check automatically
Connect a GitHub repo and this check runs on every white-box pentest - AI-validated and reported with proof, from $99 per target.
Start a pentestRelated checks
- JavaScript / TypeScript - Insecure ConfigurationCORS Wildcard Origin
- JavaScript / TypeScript - Insecure ConfigurationCORS Wildcard With Credentials
- JavaScript / TypeScript - Insecure ConfigurationCSRF Protection Disabled
- JavaScript / TypeScript - Insecure ConfigurationExpress Trust Proxy All
- JavaScript / TypeScript - Insecure ConfigurationExpress X Powered By Enabled
- JavaScript / TypeScript - Insecure ConfigurationGraphql Introspection Enabled