What this page helps you verify fast
This hub clusters every indexed record for HTTP Headers so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.
Review known vulnerability records for the WordPress plugin HTTP Headers (`http-headers`), including severity, CVE references, affected versions, and patch status.
Recent tracked CVEs on this page include CVE-2026-4132, CVE-2026-2717 and CVE-2026-1379, so operators can jump from disclosure to patch validation without scanning the full feed first.
Start with the highest-signal CVE records for this WordPress plugin before scanning the full vulnerability feed.
HTTP Headers <= 1.19.2 - Authenticated (Administrator+) External Control of File Name or Path to RCE via 'hh_htpasswd_path' and 'hh_www_authenticate_user' Parameters
HTTP Headers <= 1.18.10 - Authenticated(Administrator+) Remote Code Execution
HTTP Headers <= 1.18.8 - Authenticated(Administrator+) SQL Injection
HTTP Headers <= 1.19.2 - Authenticated (Administrator+) CRLF Injection via Custom Header Values
HTTP Headers <= 1.18.11 - Server-Side Request Forgery
HTTP Headers <= 1.19.2 - Authenticated (Administrator+) Stored Cross-Site Scripting via 'Custom Headers' Plugin Setting
HTTP Headers <= 1.18.11 - Authenticated (Administrator+) Stored Cross-Site Scripting
This hub clusters every indexed record for HTTP Headers so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.
These recent records surface the CVE strings, patch cues, and direct report links most operators need first.
The HTTP Headers plugin for WordPress is vulnerable to External Control of File Name or Path leading to Remote Code Execution in all versions up to and including 1.19.2. This is due to insuf...
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 f...
The HTTP Headers plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 1.19.2 due to insufficient input sanitization and...
Sorted by latest disclosure date so newly published issues surface first.
The HTTP Headers plugin for WordPress is vulnerable to External Control of File Name or Path leading to Remote Code Execution in all versions up to and including 1.19.2. This is due to insufficient validation of the file path stored in the 'hh_htpasswd_path' option and lack of sa...
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 m...
The HTTP Headers plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 1.19.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-le...
The HTTP Headers plugin for WordPress is vulnerable to Server-Side Request Forgery in versions up to, and including, 1.18.11 via the ajax-inspect.php file. This can allow authenticated attackers with admin access to make web requests to arbitrary locations originating from the we...
The HTTP Headers for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in versions up to, and including, 1.18.11 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level permis...
The HTTP Headers plugin for WordPress is vulnerable to Remote Code Execution in versions up to, and including, 1.18.10 via the 'http_headers_pre_update_option' function. This allows authenticated attackers with administrator-level permissions to write files and execute code on th...
The HTTP Headers plugin for WordPress is vulnerable to SQL Injection via the 'http_headers_post_import' and 'http_headers_post_export' functions in versions up to, and including, 1.18.8 due to insufficient escaping on the user supplied parameters and lack of sufficient preparatio...