Contributor-level stored XSS via unsanitized post metadata
Published Jan 9, 2026 · Updated Jan 9, 2026
Stored XSS in Header and Footer Scripts 2.3.0 and earlier allows remote authenticated users to inject scripts through post metadata. The post_meta_save handler stores the _inpost_head_script value without sanitization, and wp_head prints that value without output escaping. Contributor-level access is sufficient; opening an affected post executes the persistent script in the visitor's browser and enables actions in that visitor's WordPress session.
Summary
What happened
Stored XSS in Header and Footer Scripts 2.3.0 and earlier allows remote authenticated users to inject scripts through post metadata. The post_meta_save handler stores the _inpost_head_script value without sanitization, and wp_head prints that value without output escaping. Contributor-level access is sufficient; opening an affected post executes the persistent script in the visitor's browser and enables actions in that visitor's WordPress session.
The record
- CVE
- CVE-2025-11453
- Published
- Jan 9, 2026
- Updated
- Jan 9, 2026
- Vendor
- Anand Kumar
- Product
- Header and Footer Scripts
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 9, 2026CVE publishedPublication date reported by the CVE source.
- Jan 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=* <=2.2.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo