Stored script execution via unescaped profile names
Published Nov 19, 2024 · Updated Apr 8, 2026
Stored XSS in weLaunch WordPress GDPR & CCPA 2.0.2 and earlier allows remote attackers to inject scripts through profile-name fields. The plugin accepts gdpr_firstname and gdpr_lastname values without sufficient sanitization and later renders them without output escaping. No authentication is required to store the payload, but a site visitor must open the affected page for the script to execute in that visitor's browser.
Summary
What happened
Stored XSS in weLaunch WordPress GDPR & CCPA 2.0.2 and earlier allows remote attackers to inject scripts through profile-name fields. The plugin accepts gdpr_firstname and gdpr_lastname values without sufficient sanitization and later renders them without output escaping. No authentication is required to store the payload, but a site visitor must open the affected page for the script to execute in that visitor's browser.
The record
- CVE
- CVE-2024-10388
- Published
- Nov 19, 2024
- Updated
- Apr 8, 2026
- Vendor
- weLaunch
- Product
- WordPress GDPR & CCPA
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 19, 2024CVE publishedPublication date reported by the CVE source.
- Apr 8, 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=0 <=2.0.2
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