Unauthenticated script execution via unescaped AJAX response
Published Feb 1, 2022 · Updated Aug 2, 2024
Reflected XSS in weLaunch WordPress GDPR & CCPA before 1.9.27 allows remote attackers to execute JavaScript via a crafted AJAX request. The check_privacy_settings action returns attacker-controlled HTML without an application/json content type and fails to escape the payload before browser interpretation. Exploitation requires a victim to visit the unauthenticated AJAX endpoint; successful exploitation runs script in the victim browser under the affected site origin.
Summary
What happened
Reflected XSS in weLaunch WordPress GDPR & CCPA before 1.9.27 allows remote attackers to execute JavaScript via a crafted AJAX request. The check_privacy_settings action returns attacker-controlled HTML without an application/json content type and fails to escape the payload before browser interpretation. Exploitation requires a victim to visit the unauthenticated AJAX endpoint; successful exploitation runs script in the victim browser under the affected site origin.
The record
- CVE
- CVE-2022-0220
- Published
- Feb 1, 2022
- Updated
- Aug 2, 2024
- Vendor
- weLaunch
- Product
- WordPress GDPR & CCPA
- Classifications
- CWE-116, CWE-79, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 1, 2022CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record 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 <1.9.27
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
- WPScan check_privacy_settings reflected-XSS proof of conceptproof of concept · validated
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