A cross-origin request that the browser permits without a CORS preflight because it uses a safelisted method and header set. In security reviews, simple requests matter because they can still reach sensitive endpoints even when developers believe CORS controls are blocking cross-site abuse.
What Makes a Simple Request “Simple”
A simple request is defined by what the browser allows to go out without a CORS preflight, not by whether the target endpoint is harmless. The browser treats certain cross-origin requests as lower-friction when they use safelisted methods and a safelisted header set, which means the request can be transmitted before any preflight check would otherwise slow it down.
This matters because “simple” describes the browser’s transport rules, not the application’s security posture. A request can still carry meaningful state-changing intent, reach authenticated endpoints, or interact with sensitive server-side functionality even when developers assume cross-origin abuse is blocked by CORS enforcement.
How Simple Requests Bypass Preflight Friction
Preflight is the browser’s way of asking permission before sending requests that fall outside the simple-request rules. When a request stays within the safelisted method and header constraints, the browser skips that negotiation step and sends the request directly, which reduces visible friction for both legitimate traffic and abuse cases.
That design is useful for interoperability, but it also means developers cannot treat the absence of a preflight as evidence that the request is low-risk. The protection boundary is about browser behaviour, while the real security outcome depends on what the server accepts, how it authenticates the caller, and whether the endpoint performs side effects.
Why Simple Requests Still Matter in Web Security Reviews
Security reviews focus on simple requests because they can be used to reach endpoints that were assumed to be shielded by CORS policy alone. If an endpoint performs sensitive actions or discloses data based only on ambient browser credentials, then a cross-origin page may still be able to trigger the request even though no preflight occurs.
That makes simple requests a useful review lens for CSRF-like abuse, unsafe state changes, and over-trusting browser-side signals. The key question is not whether the browser preflights the request, but whether the server is resilient when a cross-origin request arrives with otherwise ordinary request shapes.
Common Misconceptions About “Safe” Cross-Origin Traffic
One common mistake is assuming that simple requests are harmless because they look standard to the browser. In practice, the request can still be dangerous if the application uses cookies, session state, or other ambient trust to authorize actions without an explicit anti-abuse check.
Another misconception is that CORS alone is an access control mechanism. CORS governs whether browser responses are exposed to cross-origin scripts; it does not by itself prevent a request from being sent, and it does not replace server-side authorization, origin validation, or request-specific protections.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP API Security Top 10 addresses the attack and risk surface, while OWASP ASVS, NIST SP 800-53 Rev 5, CIS Controls v8 and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP API Security Top 10 | API2 — Broken Authentication | Simple requests can reach authenticated API endpoints without preflight friction. |
| Recommendation — Require robust authentication checks on every sensitive API request path. | ||
| OWASP ASVS | V10 — OAuth and OIDC | Cross-origin request handling often intersects with browser-based auth flows and callback handling. |
| Recommendation — Validate OAuth and OIDC flows against cross-origin abuse and callback misuse. | ||
| NIST SP 800-53 Rev 5 | AC-3 — Access Enforcement | Servers must enforce access decisions on the request itself, not assume CORS blocks abuse. |
| Recommendation — Enforce authorization at the server on every state-changing request. | ||
| CIS Controls v8 | CIS-6 — Access Control Management | Simple requests highlight the need to manage who can invoke sensitive actions, regardless of browser preflight. |
| Recommendation — Limit access to sensitive functions and verify request origin assumptions. | ||
| NIST CSF 2.0 | PR.AA-05 — Authentication Management | Cross-origin request risk rises when authenticated sessions are accepted without strong request-level controls. |
| Recommendation — Apply authentication management so only intended requests are accepted. | ||
Related resources from NHI Mgmt Group
- Why do APIs with expensive parameters create more risk than simple request floods?
- Why do MCP Tasks need lifecycle controls instead of simple request tracing?
- What is the difference between a simple CORS request and a preflighted request?
- Why does a simple model API often become risky once real users or higher request volume arrive?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org