CVE-2026-1379
Stored XSS in WordPress HTTP Headers Plugin Allows Admin Script Injection
Publication date: 2026-04-22
Last updated on: 2026-04-22
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordfence | http_headers_plugin | to 1.19.2 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The HTTP Headers plugin for WordPress has a Stored Cross-Site Scripting (XSS) vulnerability in all versions up to and including 1.19.2. This vulnerability arises because the plugin does not properly sanitize input or escape output in the admin settings.
Authenticated users with administrator-level permissions or higher can exploit this flaw to inject arbitrary web scripts into pages. These scripts will execute whenever any user accesses the affected page.
This vulnerability specifically affects multi-site WordPress installations and installations where the unfiltered_html capability has been disabled.
How can this vulnerability impact me? :
This vulnerability allows an attacker with administrator-level access to inject malicious scripts that execute in the context of other users visiting the affected pages.
Such script execution can lead to theft of user credentials, session hijacking, defacement, or other malicious actions performed on behalf of the victim user.
Because the vulnerability requires high privileges and affects multi-site or restricted HTML installations, the risk is somewhat limited but still significant in those environments.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update the HTTP Headers plugin for WordPress to a version later than 1.19.2 where the issue is fixed.
Additionally, ensure that only trusted administrators have access to the plugin settings, as exploitation requires administrator-level permissions.
If possible, review and enable unfiltered_html to reduce the risk, or avoid multi-site installations where this vulnerability applies.