Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-10924: CWE-288 Authentication Bypass Using an Alternate Path or Channel in Really Simple Plugins Really Simple Security Pro multisite

0
Critical
VulnerabilityCVE-2024-10924cvecve-2024-10924cwe-288
Published: Fri Nov 15 2024 (11/15/2024, 03:18:45 UTC)
Source: CVE Database V5
Vendor/Project: Really Simple Plugins
Product: Really Simple Security Pro multisite

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

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/28/2026, 11:22:50 UTC

Technical Analysis

CVE-2024-10924 is a critical vulnerability in the Really Simple Security WordPress plugins (Free, Pro, and Pro Multisite) versions 9.0.0 through 9.1.1.1. The issue stems from improper user check error handling within the two-factor authentication REST API actions, specifically in the 'check_login_and_get_user' function. When two-factor authentication is enabled (which is disabled by default), this flaw allows unauthenticated attackers to bypass authentication controls and log in as any existing user on the WordPress site, including high-privilege accounts such as administrators. The vulnerability is categorized under CWE-288 (Authentication Bypass Using an Alternate Path or Channel), indicating that the attacker can circumvent normal authentication mechanisms by exploiting alternate API paths. The vulnerability requires no privileges or user interaction and can be exploited remotely over the network, making it highly accessible to attackers. The CVSS v3.1 score of 9.8 reflects the critical nature of this flaw, with impacts on confidentiality, integrity, and availability. No patches or official fixes are currently linked, and no known exploits have been reported in the wild, but the potential for severe damage is significant. This vulnerability could lead to full site takeover, data theft, defacement, or deployment of malicious code within affected WordPress installations.

Potential Impact

The impact of CVE-2024-10924 is severe for organizations using the affected Really Simple Security plugin versions on WordPress sites. Successful exploitation grants attackers full administrative access without authentication, enabling them to compromise site confidentiality by accessing sensitive data, alter site integrity by modifying content or configurations, and disrupt availability by disabling services or deleting content. This can lead to data breaches, loss of customer trust, defacement, ransomware deployment, or use of the compromised site as a launchpad for further attacks. Multisite installations are particularly at risk due to the broader scope of control. Given WordPress's widespread use globally, this vulnerability poses a significant risk to websites ranging from small businesses to large enterprises and government entities. The lack of required user interaction and the remote network exploit vector increase the likelihood of automated exploitation attempts once details become widely known.

Mitigation Recommendations

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.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2024-11-06T14:20:37.200Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 697395744623b1157c4bc71d

Added to database: 1/23/2026, 3:36:20 PM

Last enriched: 2/28/2026, 11:22:50 AM

Last updated: 3/23/2026, 12:36:33 PM

Views: 71

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses