Configuration cache purge via cross-site request forgery
Published Aug 14, 2025 · Updated Apr 28, 2026
Cross-site request forgery in Product Configurator for WooCommerce 1.4.4 and earlier allows remote attackers to purge configuration caches. The public record does not identify the request handler or the missing validation that lets a forged request invoke the cache-purge operation. Exploitation requires an authenticated privileged user to visit a crafted page or submit a forged form, and the bounded consequence is cache invalidation.
Summary
What happened
Cross-site request forgery in Product Configurator for WooCommerce 1.4.4 and earlier allows remote attackers to purge configuration caches. The public record does not identify the request handler or the missing validation that lets a forged request invoke the cache-purge operation. Exploitation requires an authenticated privileged user to visit a crafted page or submit a forged form, and the bounded consequence is cache invalidation.
The record
- CVE
- CVE-2025-54674
- Published
- Aug 14, 2025
- Updated
- Apr 28, 2026
- Vendor
- Marc Lacroix
- Product
- Product Configurator for WooCommerce
- Classifications
- CWE-352, CAPEC-62, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 14, 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.4.4 changes=[{"at":"1.5.0","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