Stored XSS via forged privileged-user requests
Published Feb 24, 2025 · Updated Apr 28, 2026
CSRF in Woocommerce – Loi Hamon 1.1.0 and earlier allows remote attackers to store script content via a forged privileged-user request. Public records do not disclose which action accepts the forged request or which stored field renders the attacker-controlled script. Exploitation requires a privileged user to visit or submit attacker-controlled content, after which the stored script executes for later page viewers.
Summary
What happened
CSRF in Woocommerce – Loi Hamon 1.1.0 and earlier allows remote attackers to store script content via a forged privileged-user request. Public records do not disclose which action accepts the forged request or which stored field renders the attacker-controlled script. Exploitation requires a privileged user to visit or submit attacker-controlled content, after which the stored script executes for later page viewers.
The record
- CVE
- CVE-2025-27355
- Published
- Feb 24, 2025
- Updated
- Apr 28, 2026
- Vendor
- Nicolas Grillet
- Product
- Woocommerce – Loi Hamon
- Classifications
- CWE-352, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 24, 2025CVE publishedPublication date reported by the CVE source.
- Apr 28, 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.1.0
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.
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