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 para a instalação

Repositório: xalgord/xalgorix
Última atividade na origem: 6 de junho de 2026 às 16:41
Idioma detectado do SKILL.md: inglês
Estrelas: 813
Forks: 146

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

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

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

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 todas deste repositório

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