iBryl Switch User <= 1.0.1 - Authenticated (Subscriber+) Privilege Escalation via Account Takeover
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- Plugin Name: iBryl Switch User
- Affected Version
<= 1.0.1- CVSS
- 8.8High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-49675
At a glance
CVE-2024-49675 is a high-severity Missing Authorization vulnerability in the Plugin Name WordPress plugin, affecting versions <= 1.0.1. 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. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed October 2024, reported by stealthcopter.
Vulnerability Overview
The iBryl Switch User plugin for WordPress is vulnerable to privilege escalation in all versions up to, and including, 1.0.1. This is due to the plugin not properly verifying if a user has the appropriate permissions to switch as another user. This makes it possible for authenticated attackers, with subscriber-level access and above, to access other users accounts and elevate their privileges when that account has administrative, or other, level access.
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-862: Missing Authorization
Reaching this weakness in Plugin Name <= 1.0.1 takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. No fixed build of this plugin is recorded for Plugin Name yet, so installs running <= 1.0.1 stay exposed until the vendor ships one.
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?
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. 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