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.

Ir a la instalación

Repositorio: xalgord/xalgorix
Última actividad en el origen: 6 de junio de 2026 a las 16:41
Idioma detectado de SKILL.md: inglés
Estrellas: 813
Forks: 146

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

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

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

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

Ver todos los de este repositorio

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