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-2026-4132
Score 7.2 from GitHub Security Advisory (severity: HIGH) published 2026-04-22. NVD baseline CVSS 7.2; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.2
- EG Score
- 7.2(medium)
- EG Risk
- 33(Track)EG Risk 33/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity72% × 45%Exploitation1% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 59.1%
- KEV
- Not listed
Published
April 22, 2026
Last Modified
April 22, 2026
References (13)
- security@wordfencehttps://plugins.trac.wordpress.org/browser/http-headers/tags/1.19.2/http-headers.php#L1296
- security@wordfencehttps://plugins.trac.wordpress.org/browser/http-headers/tags/1.19.2/http-headers.php#L1298
- security@wordfencehttps://plugins.trac.wordpress.org/browser/http-headers/tags/1.19.2/http-headers.php#L1403
- security@wordfencehttps://plugins.trac.wordpress.org/browser/http-headers/tags/1.19.2/http-headers.php#L671
- security@wordfencehttps://plugins.trac.wordpress.org/browser/http-headers/tags/1.19.2/http-headers.php#L722
- security@wordfencehttps://plugins.trac.wordpress.org/browser/http-headers/tags/1.19.2/http-headers.php#L97
- security@wordfencehttps://plugins.trac.wordpress.org/browser/http-headers/trunk/http-headers.php#L1296
- security@wordfencehttps://plugins.trac.wordpress.org/browser/http-headers/trunk/http-headers.php#L1298
- security@wordfencehttps://plugins.trac.wordpress.org/browser/http-headers/trunk/http-headers.php#L1403
- security@wordfencehttps://plugins.trac.wordpress.org/browser/http-headers/trunk/http-headers.php#L671
- security@wordfencehttps://plugins.trac.wordpress.org/browser/http-headers/trunk/http-headers.php#L722
- security@wordfencehttps://plugins.trac.wordpress.org/browser/http-headers/trunk/http-headers.php#L97
- security@wordfencehttps://www.wordfence.com/threat-intel/vulnerabilities/id/ce010c6f-16bd-4178-a621-31ba6378946a?source=cve
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 33× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 110 total refreshes for this CVE.
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:11 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-19 19:26 UTCEPSS rescore
- 2026-06-19 19:26 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-17 17:53 UTCEPSS rescore
- 2026-06-16 17:53 UTCEPSS rescore
- 2026-06-15 17:49 UTCEPSS rescore
- 2026-06-15 17:49 UTCEPSS rescore
- 2026-06-15 05:31 UTCGHSA enrichment
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-14 17:00 UTCGHSA enrichment
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 03:24 UTCGHSA enrichment
- 2026-06-11 14:53 UTCGHSA enrichment
- 2026-06-11 14:00 UTCEPSS rescore
- 2026-06-10 22:19 UTCEPSS rescore
- 2026-06-10 17:27 UTCGHSA enrichment
- 2026-06-10 13:22 UTCEPSS rescore
- 2026-06-10 13:22 UTCEPSS rescore
- 2026-06-10 04:55 UTCGHSA enrichment
- 2026-06-09 16:25 UTCGHSA enrichment
- 2026-06-09 03:55 UTCGHSA enrichment
- 2026-06-08 14:17 UTCEPSS rescore
- 2026-06-08 14:17 UTCEPSS rescore
- 2026-06-08 13:32 UTCGHSA enrichment
- 2026-06-08 01:01 UTCGHSA enrichment
- 2026-06-07 15:25 UTCEPSS rescore
- 2026-06-07 15:25 UTCEPSS rescore
- 2026-06-07 12:31 UTCGHSA enrichment
- 2026-06-07 00:01 UTCGHSA enrichment
- 2026-06-06 13:47 UTCEPSS rescore
- 2026-06-06 13:47 UTCEPSS rescore
- 2026-06-06 08:11 UTCGHSA enrichment
- 2026-06-05 22:47 UTCEPSS rescore
- 2026-06-05 18:51 UTCGHSA enrichment
- 2026-06-05 06:10 UTCEPSS rescore
- 2026-06-05 06:10 UTCEPSS rescore
- 2026-06-05 03:35 UTCGHSA enrichment
- 2026-06-04 14:09 UTCGHSA enrichment
- 2026-06-04 13:12 UTCEPSS rescore
- 2026-06-04 13:12 UTCEPSS rescore
- 2026-06-04 01:16 UTCGHSA enrichment
- 2026-06-03 12:46 UTCGHSA enrichment
- 2026-06-02 20:13 UTCEPSS rescore
- 2026-06-02 17:31 UTCGHSA enrichment
- 2026-06-02 05:01 UTCGHSA enrichment
- 2026-06-01 15:19 UTCGHSA enrichment
- 2026-06-01 13:52 UTCEPSS rescore
- 2026-06-01 13:52 UTCEPSS rescore
- 2026-05-31 22:30 UTCEPSS rescore
- 2026-05-31 22:30 UTCEPSS rescore
- 2026-05-31 00:16 UTCEPSS rescore
- 2026-05-31 00:16 UTCEPSS rescore
- 2026-05-29 13:44 UTCEPSS rescore
- 2026-05-29 13:44 UTCEPSS rescore
- 2026-05-28 13:44 UTCEPSS rescore
Frequently asked(5)
What is CVE-2026-4132?
When was CVE-2026-4132 disclosed?
Is CVE-2026-4132 actively exploited?
What is the CVSS score of CVE-2026-4132?
How do I remediate CVE-2026-4132?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-4132
Is Your Infrastructure Affected by CVE-2026-4132?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.