dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-11840

HIGH · 7.1 CVSS v3.1 Published 2024-12-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The RapidLoad WordPress plugin lacks capability checks on multiple AJAX functions (uucss_data, update_rapidload_settings, wp_ajax_update_htaccess_file, uucss_update_rule, upload_rules, get_all_rules, update_titan_settings, preload_page, activate_module), allowing any authenticated user with Subscriber-level access to call these functions and modify plugin settings or execute SQL injection attacks.

MitigationUpdate to version 2.4.3 or later which adds proper capability checks. Additionally, implement nonce verification and parameterized queries to prevent SQL injection on all AJAX handlers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify RapidLoad plugin is installed
    Locate the plugin in wp-content/plugins/ directory or check via WordPress admin plugins list
    Affected if RapidLoad plugin is present on the WordPress site
  2. Determine installed RapidLoad version
    Check the plugin header in the main PHP file (typically rapidload.php) for the Version field, or query via wp-cli: wp plugin list --name=rapidload
    Affected if Version is lower than 2.4.3 or the version cannot be determined (indicating outdated installation)
  3. Confirm WordPress user roles exist
    Check if any user role with Subscriber-level or higher access exists on the site by querying wp_users table or via wp-cli: wp user list
    Affected if At least one user with Subscriber role or higher exists on the site
  4. Verify AJAX endpoints are accessible
    Check if the vulnerable AJAX actions are registered by examining plugin code for do_action('wp_ajax_*') calls or by testing access to /wp-admin/admin-ajax.php with action parameters like uucss_data, update_rapidload_settings, etc.
    Affected if Any of these AJAX actions (uucss_data, update_rapidload_settings, wp_ajax_update_htaccess_file, uucss_update_rule, upload_rules, get_all_rules, update_titan_settings, preload_page, activate_module) respond without capability validation

If RapidLoad plugin versions below 2.4.3 are installed AND any authenticated user with Subscriber-level access exists, the site is vulnerable to the described privilege escalation and potential SQL injection issues.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 2.4.3 or later which adds proper capability checks. Additionally, implement nonce verification and parameterized queries to prevent SQL injection on all AJAX handlers.

Recommended fix High confidence

Version 2.4.3 or latest available version

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the RapidLoad – Optimize Web Vitals Automatically plugin
  4. Click Update Now if an update is available, or manually download the latest version from wordpress.org and upload it
  5. Verify the updated version is 2.4.3 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation5.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,310
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-11840 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-11840 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data