High severityC#Insecure ConfigurationHIGH confidence
CORS Any Origin With Credentials
A CORS policy combines AllowAnyOrigin() with AllowCredentials(), which the browser forbids and which, if forced, would expose credentialed responses to any site (CWE-942).
Standards mapping
- OWASP Top 10
- A05:2021 - Security Misconfiguration
- OWASP ASVS
- V14.5.3 (L1)
Vulnerable vs. safe
Flagged by this check
builder.AllowAnyOrigin().AllowAnyHeader().AllowCredentials();Passes - the safe pattern
builder.WithOrigins("https://app.example.com").AllowCredentials();Why it matters & how to fix it
A CORS policy combines AllowAnyOrigin() with AllowCredentials(), which the browser forbids and which, if forced, would expose credentialed responses to any site (CWE-942). Replace AllowAnyOrigin with an explicit allow-list via WithOrigins(...) when credentials are enabled, and never reflect arbitrary origins.
References
Rule ID integsec.csharp.insecure-config.cors-any-origin-with-credentials - 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 Acao Wildcard Header
- 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