HTTP Headers vulnerabilities
Plugin slug http-headers · 7 known vulnerabilities · latest disclosed 2026-04-21 · WordPress.org page
1 vulnerability has no fixed version yet. If you use this plugin, consider disabling or replacing it until a fix is released.
1 of 7 rated high or critical (CVSS 7 or more).
Known vulnerabilities in HTTP Headers
| Severity | Affected versions | Fixed in | CVE | Published | Details |
|---|---|---|---|---|---|
| High 7.2 | <= 1.19.2 | 1.19.3 | CVE-2026-4132 | 2026-04-21 | Advisory |
| Medium 5.5 | <= 1.19.5 | No fix yet | CVE-2026-2717 | 2026-04-21 | Advisory |
| Medium 4.4 | <= 1.19.4 | 1.19.5 | CVE-2026-1379 | 2026-04-21 | Advisory |
| Medium 5.5 | <= 1.18.11 | 1.19.0 | CVE-2023-37978 | 2023-07-13 | Advisory |
| Medium 4.4 | <= 1.18.11 | 1.19.0 | CVE-2023-37874 | 2023-07-10 | Advisory |
| Medium 6.6 | <= 1.18.10 | 1.18.11 | CVE-2023-1208 | 2023-06-19 | Advisory |
| Medium 6.6 | <= 1.18.8 | 1.18.9 | CVE-2023-1207 | 2023-04-24 | Advisory |
Check if a site is affected
Enter a site address to see which version of HTTP Headers and other plugins it runs, and whether they match a known vulnerability.
Questions
Is the HTTP Headers plugin safe to use?
1 known issue(s) have no fix yet, so check the table above before using it.
How do I check which version of HTTP Headers my site runs?
In WordPress go to Plugins > Installed Plugins. From the outside, the free PluginPeek scan below reads the version from the site's public files.
How do I fix a vulnerable plugin?
Make a full backup, then update it from Dashboard > Updates and check the site afterwards. If you would rather not, we can do it for a fixed $99, paid after you have checked the site.