testing-for-email-header-injection

Test web application email functionality for SMTP header injection vulnerabilities that allow attackers to inject additional email headers, modify recipients, and abuse contact forms for spam relay.

Jump to install

Repository: xalgord/xalgorix
Last source activity: June 6, 2026 at 16:41
Detected SKILL.md language: English
Stars: 813
Forks: 146

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/xalgord/xalgorix --skill testing-for-email-header-injection

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

exploiting-http-request-smuggling

Detecting and exploiting HTTP request smuggling vulnerabilities caused by Content-Length and Transfer-Encoding parsing discrepancies between front-end and back-end servers.

2026-07-20

exploiting-oauth-misconfiguration

Identifying and exploiting OAuth 2.0 and OpenID Connect misconfigurations including redirect URI manipulation, token leakage, and authorization code theft during security assessments.

2026-07-20

exploiting-subdomain-takeover-vulnerabilities

Identifying and exploiting dangling DNS records pointing to unclaimed cloud services, enabling subdomain takeover for phishing, cookie stealing, and authentication bypass during authorized penetration tests.

2026-06-19

View all from this repository

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

How to CONFIRM a Hit (avoid false negatives)

Positive signal: an injected CRLF actually adds a header or recipient that takes effect — a copy of the email lands in your attacker-controlled (e.g. agentmail) inbox via injected Cc/Bcc, or From/Reply-To is overridden in the delivered message.

Confirm by inspecting the raw source / "Show Original" of a RECEIVED email for your injected Cc:, Bcc:, From:, Reply-To:, or overridden body — do not rely on the form returning success.

An HTTP 200 from the form is NOT a hit (the app may strip newlines); a single failed payload is NOT a clean negative until encodings and fields are varied.

Do NOT conclude "not vulnerable" until you have tried:

Every newline encoding: %0A (LF), %0D%0A (CRLF), %0D (CR), raw \r\n in JSON, and double-encoding (%250A).
Every injection point: email, name, subject, reply-to and any field reflected into headers.
Recipient injection (Bcc/Cc/extra To) to prove spam-relay, plus MIME/body override (Content-Type, boundaries) to prove content control.
Confirming actual delivery to your test inbox (wait for the email), not merely that the server accepted the payload.

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