CVE-2026-4132The 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.
Updated under an hour ago ()
Does this affect you?
It lists no affected products yet. Add what you run and Signals checks it as products are added.
No exploitation reported and no EPSS estimate yet.
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.
- CVSS
- 7.2 HIGH (v3.1, NVD)CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- CWE-73
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Not given
- NVD analysis
- Deferred
- Record last updated
- Jun 17, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
No affected products are listed yet.
References
- https://plugins.trac.wordpress.org/browser/http-headers/tags/1.19.2/http-headers.php#L1296
- https://plugins.trac.wordpress.org/browser/http-headers/tags/1.19.2/http-headers.php#L1298
- https://plugins.trac.wordpress.org/browser/http-headers/tags/1.19.2/http-headers.php#L1403
- https://plugins.trac.wordpress.org/browser/http-headers/tags/1.19.2/http-headers.php#L671
- https://plugins.trac.wordpress.org/browser/http-headers/tags/1.19.2/http-headers.php#L722
- https://plugins.trac.wordpress.org/browser/http-headers/tags/1.19.2/http-headers.php#L97
- https://plugins.trac.wordpress.org/browser/http-headers/trunk/http-headers.php#L1296
- https://plugins.trac.wordpress.org/browser/http-headers/trunk/http-headers.php#L1298
- https://plugins.trac.wordpress.org/browser/http-headers/trunk/http-headers.php#L1403
- https://plugins.trac.wordpress.org/browser/http-headers/trunk/http-headers.php#L671
- https://plugins.trac.wordpress.org/browser/http-headers/trunk/http-headers.php#L722
- https://plugins.trac.wordpress.org/browser/http-headers/trunk/http-headers.php#L97
- https://www.wordfence.com/threat-intel/vulnerabilities/id/ce010c6f-16bd-4178-a621-31ba6378946a?source=cve
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.