# CVE-2024-37560: WordPress WP User Switch plugin <= 1.1.0 - Privilege Escalation vulnerability

> An improper privilege management flaw in the WP User Switch plugin allows attackers to escalate privileges within the WordPress environment.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Jul 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-qjjp-x73m-9gv4

## What is CVE-2024-37560?

CVE-2024-37560 is a high-severity vulnerability in IqbalRony WP User Switch, published on 12 Jul 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Improper Privilege Management vulnerability in IqbalRony WP User Switch allows Privilege Escalation.This issue affects WP User Switch: from n/a through 1.1.0.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2024-37560?


## How do I fix CVE-2024-37560?

No fix has been published for CVE-2024-37560 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-37560 being exploited?

There is no known exploitation of CVE-2024-37560 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-37560 and fix it if it is affected.

What it is: CVE-2024-37560 is a high-severity vulnerability in IqbalRony WP User Switch, published on 12 Jul 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-37560 in the wild and no public exploit code.

Affected product: IqbalRony WP User Switch. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-37560/ (Markdown: https://insights.sbomify.com/CVE-2024-37560/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-37560
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-37560
- OSV: https://osv.dev/vulnerability/CVE-2024-37560

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-37560/
Summaries are generated and may contain mistakes; the official description above is the record.