# CVE-2026-8293: Really Simple Security < 9.5.10.1 - Authentication Bypass via Two-Factor OTP Skip

> Attackers can bypass two-factor authentication in the Really Simple Security WordPress plugin to gain unauthorized access to user accounts.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/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:** 2 Jun 2026
- **Updated:** 2 Jun 2026
- **Also known as:** GHSA-g33r-3vq8-q6f4

## What is CVE-2026-8293?

CVE-2026-8293 is a high-severity authentication bypass vulnerability in Unknown Really Simple Security, published on 2 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Really Simple Security  WordPress plugin before 9.5.10.1 does not enforce the second-factor challenge in two of its two-factor authentication REST endpoints, allowing an attacker who knows a user's password to obtain a WordPress authentication session for that user without completing the email OTP challenge.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-8293?


## How do I fix CVE-2026-8293?

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

## Is CVE-2026-8293 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8293 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-8293 and fix it if it is affected.

What it is: CVE-2026-8293 is a high-severity authentication bypass vulnerability in Unknown Really Simple Security, published on 2 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8293 exists.

Affected product: Unknown Really Simple Security. 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-2026-8293/ (Markdown: https://insights.sbomify.com/CVE-2026-8293/index.md)
```

## Sources

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

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