CVE-2024-11840

RapidLoad – Optimize Web Vitals Automatically <= 2.4.2 - Missing Authorization to Authenticated (Subscriber+) Plugin Settings Modification and SQL Injection

2024-12-10 00:00
Lucio Sá

Strategic Overview

Status
Patched in 2.4.3
Affected Plugin
RapidLoad AI – Optimize Web Vitals Automatically
Affected Version
<= 2.4.2
CVSS
7.1High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-11840
View all RapidLoad AI – Optimize Web Vitals Automatically vulnerabilities

At a glance

CVE-2024-11840 is a high-severity Missing Authorization vulnerability in the RapidLoad AI WordPress plugin, affecting versions <= 2.4.2. It carries a CVSS score of 7.1 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.4.3; sites on affected versions should update now. Disclosed December 2024, reported by Lucio Sá.

Vulnerability Overview

The RapidLoad – Optimize Web Vitals Automatically plugin for WordPress is vulnerable to unauthorized access of data and modification of data due to a missing capability check on the uucss_data, update_rapidload_settings, wp_ajax_update_htaccess_file, uucss_update_rule, upload_rules, get_all_rules, update_titan_settings, preload_page, and activate_module functions in all versions up to, and including, 2.4.2. This makes it possible for authenticated attackers, with Subscriber-level access and above, to modify plugin settings or conduct SQL injection attacks.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality.

CWE-862: Missing Authorization

Reaching this weakness in RapidLoad AI <= 2.4.2 takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For RapidLoad AI the fix is 2.4.3: builds <= 2.4.2 are affected, anything from 2.4.3 onward is not.

Remediation

Update to version 2.4.3, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: RapidLoad AI 2.4.3 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-11840https://www.wordfence.com/threat-intel/vulnerabilities/id/2c8ff4ec-9b40-4d59-b3b0-382f91042a4ahttps://nvd.nist.gov/vuln/detail/CVE-2024-11840

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C