Subscriber-level stored XSS via unsanitized component names
Published Apr 27, 2024 · Updated Apr 8, 2026
Stored XSS in WPClever WPC Composite Products for WooCommerce 7.2.7 and earlier allows remote authenticated users to inject scripts. The ajax_save_components function accepts wooco_components[0][name] without adequate authorization or input sanitization, then exposes it without sufficient output escaping. Subscriber-level access is sufficient, and the stored script executes whenever a user opens the affected page, enabling actions in that user's browser context.
Summary
What happened
Stored XSS in WPClever WPC Composite Products for WooCommerce 7.2.7 and earlier allows remote authenticated users to inject scripts. The ajax_save_components function accepts wooco_components[0][name] without adequate authorization or input sanitization, then exposes it without sufficient output escaping. Subscriber-level access is sufficient, and the stored script executes whenever a user opens the affected page, enabling actions in that user's browser context.
The record
- CVE
- CVE-2024-2838
- Published
- Apr 27, 2024
- Updated
- Apr 8, 2026
- Vendor
- WPClever
- Product
- WPC Product Bundles for WooCommerce
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 27, 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 <=7.2.7
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
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