HTTP Headers <= 1.19.2 - Authenticated (Administrator+) CRLF Injection via Custom Header Values
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- HTTP Headers
- Affected Version
<= 1.19.2- CVSS
- 5.5Medium
- Weakness type
- CWE-93 · Improper Neutralization of CRLF Sequences ('CRLF Injection')
- CVE
CVE-2026-2717
At a glance
CVE-2026-2717 is a medium-severity Improper Neutralization of CRLF Sequences ('CRLF Injection') vulnerability in the HTTP Headers WordPress plugin, affecting versions <= 1.19.2. It carries a CVSS score of 5.5 (reachable over the network; low attack complexity; high availability impact). Exploitation requires an authenticated account at Administrator level or above. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed April 2026, reported by Kai Aizen.
Vulnerability Overview
The HTTP Headers plugin for WordPress is vulnerable to CRLF Injection in all versions up to, and including, 1.19.2. This is due to insufficient sanitization of custom header name and value fields before writing them to the Apache .htaccess file via `insert_with_markers()`. This makes it possible for authenticated attackers, with Administrator-level access and above, to inject arbitrary newline characters and additional Apache directives into the .htaccess configuration file via the 'Custom Headers' settings, leading to Apache configuration parse errors and potential site-wide denial of service.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on availability.
CWE-93: Improper Neutralization of CRLF Sequences ('CRLF Injection')
The product uses CRLF (carriage return line feeds) as a special element, e.g. to separate lines or records, but it does not neutralize or incorrectly neutralizes CRLF sequences from inputs.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
No patched version is recorded yet, so there is nothing to update to; WordSec's vulnerability alerts flag this record the moment that changes.
- Alerts
External References
Related records
Other vulnerabilities in HTTP Headers
- 7.2CVE-2026-4132: HTTP Headers External Control of File Name or Path
CVE-2026-4132 - 6.6CVE-2023-1208: HTTP Headers <= 1.18.10 Remote Code Execution
CVE-2023-1208 - 6.6CVE-2023-1207: HTTP Headers <= 1.18.8 SQL Injection
CVE-2023-1207 - 5.5CVE-2023-37978: HTTP Headers <= 1.18.11 Server-Side Request Forgery
CVE-2023-37978 - 4.4CVE-2026-1379: HTTP Headers <= 1.19.4 Stored Cross-Site Scripting
CVE-2026-1379 - 4.4CVE-2023-37874: HTTP Headers <= 1.18.11 Stored Cross-Site Scripting
CVE-2023-37874
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C