Skip to main content
CVE-2024-10924VulnerabilityPublished Updated

CVE-2024-10924: Really Simple Security Pro multisite (WordPress plugin) · Authentication Bypass Using an Alternate Path or Channel

Affects Really Simple Security Pro multisite (WordPress plugin)Source CVE Database V5

0

Not known to be exploited · public exploit available (Metasploit, Exploit-DB) · 82% EPSS · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
82.2% chance of exploitation in 30 days – higher than 99% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 15 Nov 2024

  2. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  3. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by Wordfence

    , 9 days before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. First Exploit-DB entry (opens in a new tab)

    Really Simple Security 9.1.1.1 - Authentication Bypass

    , 151 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
Really Simple Plugins Really Simple Security Pro multisiteAffected
  • =9.0.0
Fixed in–

AI-suggested

Organizations should immediately verify if they are running Really Simple Security plugin versions 9.0.0 through 9.1.1.1 and assess whether two-factor authentication is enabled. Until an official patch is released, the following mitigations are recommended: 1) Disable the Really Simple Security plugin or specifically disable the two-factor authentication feature within the plugin to prevent exploitation. 2) Restrict access to the WordPress REST API endpoints related to authentication by implementing web application firewall (WAF) rules or IP whitelisting to limit exposure. 3) Monitor authentication logs for suspicious login attempts or anomalies indicating potential exploitation. 4) Apply principle of least privilege by limiting administrator accounts and enforcing strong password policies. 5) Regularly back up site data and configurations to enable recovery in case of compromise. 6) Stay updated with vendor advisories and apply patches immediately once available. 7) Consider alternative two-factor authentication plugins with verified security if continued two-factor protection is required.

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).

References

Community reviews

Loading reviews…