Findings

CVE-2026-2717

The HTTP Headers plugin for WordPress is vulnerable to CRLF Injection in all versions up to, and including, 1.19.2.

Published Apr 22, 2026 · updated Jun 17, 2026

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 . 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.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Apr 22, 2026 · NIST NVD

    Detected

    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 . This makes it possible for authenticated attackers, with Administrator-level access and above, to inject arbitrary newline characters and additional

  2. Jun 17, 2026 · NIST NVD

    Updated

    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 . This makes it possible for authenticated attackers, with Administrator-level access and above, to inject arbitrary newline characters and additional

Sources

  • CVE.orgVulnerability recordCVE-2026-2717

    Official CVE identifier

    cve.org
  • NIST NVDVulnerability recordCVE-2026-2717

    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 . This m

    nvd.nist.gov

References

CVE-2026-2717 · ZeroDay Findings