php-crlf-audit

Identifies CRLF injection vulnerabilities in PHP HTTP headers and cookies.

386|38|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/0xShe/PHP-Code-Audit-Skill --skill php-crlf-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: php-crlf-audit
Source: https://github.com/0xShe/PHP-Code-Audit-Skill/tree/main/php-crlf-audit
Command: npx skills add https://github.com/0xShe/PHP-Code-Audit-Skill --skill php-crlf-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PHP CRLF/HTTP response splitting vulnerabilities can allow attackers to manipulate response headers and cookies, leading to header injection, cache poisoning, or redirects.

Core Features & Use Cases

  • Detect user-controlled data entering headers and cookies
  • Analyze line breaks and encoding to identify injection vectors
  • Provide PoC guidance and remediation recommendations (no omission)

Quick Start

Scan a PHP project to identify CRLF injection points in headers and cookies and generate PoC-based remediation guidance.

Frequently Asked Questions about php-crlf-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect CRLF injection vulnerabilities in PHP source code?

Detect CRLF injection vulnerabilities in PHP by tracing user-controlled data into HTTP response headers, cookies, or header-like outputs to identify injection vectors and generate remediation guidance.

What is HTTP response splitting and how does it affect PHP web applications?

HTTP response splitting in PHP web applications allows attackers to manipulate response headers and cookies using CRLF characters, leading to header injection, cache poisoning, or unauthorized redirects.

How do I audit PHP frameworks for HTTP header injection risks?

Audit PHP frameworks for HTTP header injection risks by analyzing header construction, output encoding, and detecting CRLF-related anomalies across the source code to pinpoint user-controlled data entering headers.

Can I generate a PoC for CRLF vulnerabilities during a PHP security audit?

Yes, you can generate a proof-of-concept for CRLF vulnerabilities during a PHP security audit to demonstrate header manipulation risks and receive explicit remediation recommendations with structured evidence points.

What is the best way to find cookie injection vectors in PHP?

Find cookie injection vectors in PHP by tracing untrusted user input into cookie construction functions and analyzing line breaks and encoding to detect CRLF anomalies and response splitting risks.

Why does user input cause CRLF anomalies in PHP response headers?

User input causes CRLF anomalies in PHP response headers when untrusted data containing line break characters is directly inserted into header construction without proper output encoding or normalization.