User Toolkit <= 1.2.3 - Authenticated (Subscriber+) Authentication Bypass
Strategic Overview
- Status
- Patched in 1.2.4
- Affected Plugin
- User Toolkit
- Affected Version
<= 1.2.3- CVSS
- 8.8High
- Weakness type
- CWE-288 · Authentication Bypass Using an Alternate Path or Channel
- CVE
CVE-2024-9890
At a glance
CVE-2024-9890 is a high-severity Authentication Bypass Using an Alternate Path or Channel vulnerability in the User Toolkit WordPress plugin, affecting versions <= 1.2.3. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.2.4; sites on affected versions should update now. Disclosed October 2024, reported by István Márton.
Vulnerability Overview
The User Toolkit plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 1.2.3. This is due to an improper capability check in the 'switchUser' function. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to log in as any existing user on the site, such as an administrator. CVE-2024-50503 may be a duplicate.
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 interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-288: Authentication Bypass Using an Alternate Path or Channel
User Toolkit <= 1.2.3 carries this weakness at switchUser, and reaching it takes an account at Subscriber level or above. Authentication bypass through an alternate path means the application has a second route to a protected action that skips the checks the primary route performs.
The protection on the main path becomes irrelevant, because the attacker simply uses the route that never asks. For User Toolkit the fix is 1.2.4: builds <= 1.2.3 are affected, anything from 1.2.4 onward is not.
Remediation
Update to version 1.2.4, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: User Toolkit 1.2.4 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in User Toolkit
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C