Stored XSS via unsanitized Results Header
Published Nov 21, 2022 · Updated Apr 29, 2025
Stored XSS in WBCE CMS 1.5.4 allows remote authenticated users to execute scripts in a victim's browser through Search Settings. The Results Header field stores crafted markup and emits it on search results without neutralizing script-capable input. Exploitation requires access to Search Settings and a victim who loads a search results page; the script runs in that victim's browser context.
Summary
What happened
Stored XSS in WBCE CMS 1.5.4 allows remote authenticated users to execute scripts in a victim's browser through Search Settings. The Results Header field stores crafted markup and emits it on search results without neutralizing script-capable input. Exploitation requires access to Search Settings and a victim who loads a search results page; the script runs in that victim's browser context.
The record
- CVE
- CVE-2022-45014
- Published
- Nov 21, 2022
- Updated
- Apr 29, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 21, 2022CVE publishedPublication date reported by the CVE source.
- Apr 29, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- WBCE Results Header stored-XSS reproductionproof of concept · unverified
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