CVE-2026-2717
The HTTP Headers plugin for WordPress is vulnerable to CRLF …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- plugins.trac.wordpress.org/browser/http-headers/tags/1.19.2/http-headers.php#L1098
- plugins.trac.wordpress.org/browser/http-headers/tags/1.19.2/http-headers.php#L745
- plugins.trac.wordpress.org/browser/http-headers/trunk/http-headers.php#L1098
- plugins.trac.wordpress.org/browser/http-headers/trunk/http-headers.php#L745
- www.wordfence.com/threat-intel/vulnerabilities/id/7716e77f-e899-4046-9421-86fc0c36c245?sou
- nvd.nist.gov/vuln/detail/CVE-2026-2717
- cve.org/CVERecord?id=CVE-2026-2717
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.