Stored XSS via unsanitized tooltip content
Published Oct 29, 2025 · Updated Oct 29, 2025
Stored XSS in Automattic WooCommerce 10.0.2 and earlier allows remote authenticated users to execute scripts through payment settings. The payment-configuration path stores legacy title, description, and order values without sufficient sanitization, then inserts them into jQuery tooltip HTML without DOMPurify. Shop Manager access and a victim viewing the affected tooltip are required, bounding the consequence to script execution in that viewer's browser.
Summary
What happened
Stored XSS in Automattic WooCommerce 10.0.2 and earlier allows remote authenticated users to execute scripts through payment settings. The payment-configuration path stores legacy title, description, and order values without sufficient sanitization, then inserts them into jQuery tooltip HTML without DOMPurify. Shop Manager access and a victim viewing the affected tooltip are required, bounding the consequence to script execution in that viewer's browser.
The record
- CVE
- CVE-2025-49042
- Published
- Oct 29, 2025
- Updated
- Oct 29, 2025
- Vendor
- WooCommerce
- Product
- WooCommerce
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 29, 2025CVE publishedPublication date reported by the CVE source.
- Oct 29, 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=n/a <=10.0.2 changes=[{"at":"10.0.3","status":"unaffected"}]
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