Reflected XSS via unescaped HTML attributes
Published Dec 26, 2022 · Updated Apr 14, 2025
Reflected XSS in Booster for WooCommerce before 5.6.3 allows remote attackers to execute script through crafted URLs. HTML attribute output paths write certain attacker-controlled URLs and parameters without context-appropriate escaping. Booster Plus and Elite before 6.0.0 are also affected; a user must open the crafted request, after which script runs in the site's browser origin.
Summary
What happened
Reflected XSS in Booster for WooCommerce before 5.6.3 allows remote attackers to execute script through crafted URLs. HTML attribute output paths write certain attacker-controlled URLs and parameters without context-appropriate escaping. Booster Plus and Elite before 6.0.0 are also affected; a user must open the crafted request, after which script runs in the site's browser origin.
The record
- CVE
- CVE-2022-4227
- Published
- Dec 26, 2022
- Updated
- Apr 14, 2025
- Vendor
- Pluggabl LLC
- Product
- Booster for WooCommerce
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 26, 2022CVE publishedPublication date reported by the CVE source.
- Apr 14, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <5.6.3
What conditions does exploitation require?
What is affected?
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