Ecommerce Affiliate <= 1.0.0 - Unauthenticated Account Takeover visa Brute Force
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- Ecommerce Affiliate
- Affected Version
<= 1.0.0- CVSS
- 9.8Critical
- Weakness type
- CWE-307 · Improper Restriction of Excessive Authentication Attempts
- CVE
CVE-2026-106015
At a glance
CVE-2026-106015 is a critical-severity Improper Restriction of Excessive Authentication Attempts vulnerability in the Ecommerce Affiliate WordPress plugin, affecting versions <= 1.0.0. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed November 2026, reported by Enrico Marcolini.
Vulnerability Overview
The Ecommerce Affiliate plugin for WordPress is vulnerable to Account Takeover in all versions up to, and including, 1.0.0. This is due to missing ownership validation on OTP issuance and verification endpoints, combined with the absence of any rate limiting on verification attempts. This makes it possible for unauthenticated attackers to issue and brute-force one-time passwords for any account, thereby gaining full control of that account, up to and including administrator-level accounts.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-307: Improper Restriction of Excessive Authentication Attempts
The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C