Subscriber-level account takeover through broken authentication
Published May 23, 2025 · Updated May 12, 2026
Broken authentication in Subaccounts for WooCommerce 1.6.6 and earlier allows remote authenticated users to take over accounts. The vendor changelog states only that 1.6.7 fixes broken authentication, and no public source names the flawed request path, function, or validation check. Subscriber access is required, and successful abuse grants control of another WordPress account without user interaction.
Summary
What happened
Broken authentication in Subaccounts for WooCommerce 1.6.6 and earlier allows remote authenticated users to take over accounts. The vendor changelog states only that 1.6.7 fixes broken authentication, and no public source names the flawed request path, function, or validation check. Subscriber access is required, and successful abuse grants control of another WordPress account without user interaction.
The record
- CVE
- CVE-2025-47461
- Published
- May 23, 2025
- Updated
- May 12, 2026
- Vendor
- mediaticus
- Product
- Subaccounts for WooCommerce
- Classifications
- CWE-288, CAPEC-114, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 23, 2025CVE publishedPublication date reported by the CVE source.
- May 12, 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.6.6 changes=[{"at":"1.6.7","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