Unauthenticated stored XSS via unescaped api_key output
Published Mar 29, 2024 · Updated Apr 8, 2026
Stored XSS in WP ERP 1.13.1 and earlier allows remote attackers to inject scripts through the unauthenticated api_key parameter. The bundled Google API client example index.php accepts the parameter without sufficient sanitization and outputs it without escaping. No account is required; the stored payload executes when a user later opens the injected page, enabling browser-context data access or modification.
Summary
What happened
Stored XSS in WP ERP 1.13.1 and earlier allows remote attackers to inject scripts through the unauthenticated api_key parameter. The bundled Google API client example index.php accepts the parameter without sufficient sanitization and outputs it without escaping. No account is required; the stored payload executes when a user later opens the injected page, enabling browser-context data access or modification.
The record
- CVE
- CVE-2024-0609
- Published
- Mar 29, 2024
- Updated
- Apr 8, 2026
- Vendor
- HappyAddons
- Product
- WP ERP
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 29, 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 <=1.13.1
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