# CVE-2024-49675: WordPress iBryl Switch User plugin <= 1.0.1 - Account Takeover vulnerability

> An authentication bypass in the iBryl Switch User plugin allows attackers to take over accounts without valid credentials.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 23 Oct 2024
- **Updated:** 12 May 2026
- **Also known as:** GHSA-cjg2-8rvr-p7jc

## What is CVE-2024-49675?

CVE-2024-49675 is a high-severity authentication bypass vulnerability in Vitalii iBryl Switch User, published on 23 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Authentication Bypass Using an Alternate Path or Channel vulnerability in Vitalii iBryl Switch User ibryl-switch-user allows Authentication Bypass.This issue affects iBryl Switch User: from n/a through <= 1.0.1.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

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

It affects 1 product.


Products: Vitaliibryl Switch User.

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

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

## Is CVE-2024-49675 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-49675 is a high-severity authentication bypass vulnerability in Vitalii iBryl Switch User, published on 23 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-49675 in the wild and no public exploit code.

Affected product: Vitalii iBryl Switch User. 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-49675/ (Markdown: https://insights.sbomify.com/CVE-2024-49675/index.md)
```

## Sources

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

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