Radar sectionsDatabase
Check my site
WordPress plugin

HTTP Headers <= 1.19.5 — Authenticated (Administrator+) CRLF Injection via Custom Header Values

CVE-2026-2717Published · Updated

Action summary

Affected: ≤1.19.5No patch available

What to do until a fix ships
Severity
Medium5.5
CVSS
5.5
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:H
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:H Privileges required
High
UI:N User interaction
None
S:U Scope
Unchanged
C:N Confidentiality
None
I:L Integrity
Low
A:H Availability
High
Weakness
CWE-93 Improper Neutralization of CRLF Sequences
Required access
Unknown
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

HTTP Headers http-headers

  1. Affected≤ 1.19.5
  2. PatchedNo fix yet

No patched version available.

You are affected if you run ≤ 1.19.5. No fixed version has been released.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under HTTP Headers.
  • No admin access? Run a passive check of your site. It reads public files only.

What to do

  1. 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.
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch HTTP Headers to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Kai Aizen.

The HTTP Headers plugin for WordPress is vulnerable to CRLF Injection in all versions up to, and including, 1.19.5. 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.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in HTTP Headers

All 7
More vulnerabilities in HTTP Headers
SeverityVulnerabilityCVEPublished
High7.2Authenticated (Administrator+) External Control of File Name or Path to RCE via 'hh_htpasswd_path' and 'hh_www_authenticate_user' Parameters
≤1.19.2Update to 1.19.3
CVE-2026-4132
Medium4.4Authenticated (Administrator+) Stored Cross-Site Scripting via 'Custom Headers' Plugin Setting
≤1.19.4Update to 1.19.5
CVE-2026-1379
Medium5.5Server-Side Request Forgery
≤1.18.11Update to 1.19.0
CVE-2023-37978
Medium4.4Authenticated (Administrator+) Stored Cross-Site Scripting
≤1.18.11Update to 1.19.0
CVE-2023-37874
Medium6.6Authenticated(Administrator+) Remote Code Execution
≤1.18.10Update to 1.18.11
CVE-2023-1208

Timeline

  1. CVE published

    Severity medium, CVSS 5.5

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
CVE® identifiers
Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?