CVE-2024-37560
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper Privilege Management vulnerability in IqbalRony WP User Switch allows Privilege Escalation.This issue affects WP User Switch: from n/a through 1.1.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is a privilege escalation vulnerability in the WP User Switch WordPress plugin. The Improper Privilege Management vulnerability allows authenticated users to switch to higher-privilege accounts (such as administrator accounts) without proper authorization checks, enabling them to gain elevated permissions they should not have.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify WP User Switch plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WP User Switch' in the list. Alternatively, check the plugins directory /wp-content/plugins/ for a folder named 'wp-user-switch' or similar, and open the main plugin file to read the version header.Affected if The plugin is present on the WordPress site
-
Identify the installed version numberIn the WordPress plugins list, view the plugin details to see the version number, or open the main plugin PHP file (usually wp-user-switch.php or index.php) and look for the 'Version:' comment in the file header.Affected if The version is 1.1.0 or lower (the vulnerability exists in versions up to and including 1.1.0)
-
Check if user switching capability is activeLook for the user switch functionality in the WordPress admin toolbar or user profile pages. Users with lower privileges (such as subscribers or editors) should normally not have access to switch accounts. Check if non-admin users have the 'switch_users' capability assigned by examining user roles in Users > All Users and checking role capabilities.Affected if Lower-privileged users can access or see user switching options, or the 'switch_users' capability is granted to roles below administrator
-
Audit user accounts for unauthorized privilege escalationReview all user accounts in Users > All Users. Compare current user roles against expected roles. Check user_meta tables for any unexpected capability additions. Look for users who have elevated access they should not possess based on their registered role.Affected if Users exist with higher privileges than their original role, or unauthorized capability modifications are found
A user is affected if the WP User Switch plugin version 1.1.0 or lower is installed and non-admin users can access or use the user switching functionality to elevate their privileges.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate WP User Switch to a version beyond 1.1.0 that contains the privilege management fix. Until patched, restrict or disable the user switch functionality and audit user accounts for unauthorized privilege escalation.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37560 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-37560 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data