# CVE-2024-10924: Really Simple Security (Free, Pro, and Pro Multisite) 9.0.0 - 9.1.1.1 - Authentication Bypass

> Unauthenticated attackers can bypass two-factor authentication to log in as any user, including administrators, if the feature is enabled.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Nov 2024
- **Updated:** 23 Jan 2026
- **Also known as:** GHSA-f75h-cwp9-8h5x

## What is CVE-2024-10924?

CVE-2024-10924 is a critical authentication bypass vulnerability in Really Simple Security Pro, published on 15 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Really Simple Security (Free, Pro, and Pro Multisite) plugins for WordPress are vulnerable to authentication bypass in versions 9.0.0 to 9.1.1.1. This is due to improper user check error handling in the two-factor REST API actions with the 'check_login_and_get_user' function. This makes it possible for unauthenticated attackers to log in as any existing user on the site, such as an administrator, when the "Two-Factor Authentication" setting is enabled (disabled by default).

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

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

It affects 1 product.


Products: Really-Simple-Plugins Really Simple Security.

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

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

## Is CVE-2024-10924 being exploited?

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

Public exploit code:

- Exploits Really Simple Security < 9.1.2 authentication bypass (CVE-2024-10924). (github_poc): https://github.com/m3ssap0/wordpress-really-simple-security-authn-bypass-exploit
- Unauthenticated authentication bypass to RCE exploit for CVE-2024-10924. Abuses an authentication and 2FA bypass in the Really Simple Security WordPress plugin to impersonate an admin user, upload a malicious plugin, and achieve remote command execution via an interactive shell. (github_poc): https://github.com/JoshuaProvoste/0-click-RCE-Exploit-for-CVE-2024-10924
- WARNING: This is a vulnerable application to test the exploit for the Really Simple Security < 9.1.2 authentication bypass (CVE-2024-10924). Run it at your own risk! (github_poc): https://github.com/m3ssap0/wordpress-really-simple-security-authn-bypass-vulnerable-application
- Bypass del MFA en WordPress con el plugin Really Simple Security instalado entre las versiones 9.0.0 – 9.1.1.1. (github_poc): https://github.com/Maalfer/CVE-2024-10924-PoC
-  Really Simple Security (Free, Pro, and Pro Multisite) 9.0.0 – 9.1.1.1 – Authentication Bypass (github_poc): https://github.com/RandomRobbieBF/CVE-2024-10924
- https://github.com/D1se0/CVE-2024-10924-Bypass-MFA-Wordpress-LAB (github_poc): https://github.com/D1se0/CVE-2024-10924-Bypass-MFA-Wordpress-LAB

## Fix prompt for AI coding agents

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

What it is: CVE-2024-10924 is a critical authentication bypass vulnerability in Really Simple Security Pro, published on 15 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-10924 exists.

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

## Sources

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

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