HomeWordPress vulnerabilitiesHTTP Headers
HTTP Headers vulnerabilities
HTTP Headers has 5 known vulnerabilities in this database. The most recent published record is dated 22 Apr 2026.
- Known vulnerabilities
- 5
- Active installs
- 50,000+
- Latest version
- 1.19.5
- Last updated
- 27 Apr 2026
- Most recent
- 22 Apr 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Remote code execution CVE-2026-4132 | High 7.2 | Up to 1.19.2 | Fixed in a later version (latest 1.19.5) | 22 Apr 2026 |
| Denial of service CVE-2026-2717 | Medium 5.5 | Up to 1.19.2 | Fixed in a later version (latest 1.19.5) | 22 Apr 2026 |
| Cross-site scripting (XSS) CVE-2026-1379 | Medium 4.4 | Up to 1.19.2 | Fixed in a later version (latest 1.19.5) | 22 Apr 2026 |
| Remote code execution CVE-2023-1208 | High 7.2 | Before 1.18.11 | Fixed in 1.18.11 | 10 Jul 2023 |
| SQL injection CVE-2023-1207 | High 7.2 | Before 1.18.8 | Fixed in 1.18.8 | 15 May 2023 |
Read the published descriptions
- CVE-2026-4132, 22 Apr 2026
- 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 sanitization on the 'hh_www_authenticate_user' option value. The plugin allows administrators to set an arbitrary file path for the htpasswd file location and does not validate that the path has a safe file extension (e.g., restricting to .htpasswd). Additionally, the username field used for HTTP Basic Authentication is written directly into the file without sanitization. The apache_auth_credentials() function constructs the file content using the unsanitized username via sprintf('%s:{SHA}%s', $user, ...), and update_auth_credentials() writes this content to the attacker-controlled path via file_put_contents(). This makes it possible for authenticated attackers, with Administrator-level access and above, to write arbitrary content (including PHP code) to arbitrary file paths on the server, effectively achieving Remote Code Execution. CVE record
- CVE-2026-2717, 22 Apr 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 `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. CVE record
- CVE-2026-1379, 22 Apr 2026
- 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-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled. CVE record
- CVE-2023-1208, 10 Jul 2023
- This HTTP Headers WordPress plugin before 1.18.11 allows arbitrary data to be written to arbitrary files, leading to a Remote Code Execution vulnerability. CVE record
- CVE-2023-1207, 15 May 2023
- This HTTP Headers WordPress plugin before 1.18.8 has an import functionality which executes arbitrary SQL on the server, leading to an SQL Injection vulnerability. CVE record
What to do if you run HTTP Headers
If you run HTTP Headers, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new HTTP Headers vulnerabilities
Free. We email you when a new vulnerability is published for HTTP Headers, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.