dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2024-10124

CRITICAL · 9.8 CVSS v3.1 Published 2024-12-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Vayu Blocks – Gutenberg Blocks for WordPress & WooCommerce plugin for WordPress is vulnerable to unauthorized arbitrary plugin installation and activation due to a missing capability check on the tp_install() function in all versions up to, and including, 1.1.1. This makes it possible for unauthenticated attackers to install and activate arbitrary plugins which can be leveraged to achieve remote code execution if another vulnerable plugin is installed and activated. This vulnerability was partially patched in version 1.1.1.

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 Vayu Blocks WordPress plugin lacks a capability check on the tp_install() function, allowing unauthenticated attackers to install and activate arbitrary plugins. This critical flaw enables remote code execution when combined with other vulnerable plugins.

MitigationImmediately update Vayu Blocks to the latest version and audit the site for any unauthorized plugins that may have been installed exploiting this vulnerability.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Confirm Vayu Blocks plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or run 'wp plugin list --search="vayu"' via WP-CLI to list plugins containing 'vayu' in the name
    Affected if The Vayu Blocks plugin appears in the installed plugins list
  2. Identify the installed version
    In wp-admin, click 'View details' on the Vayu Blocks plugin to see the version number; alternatively, inspect the main plugin file (typically vayu-blocks.php) and look for the 'Version' header in the plugin comment block
    Affected if The displayed version is lower than 1.1.1 (e.g., 1.1.0 or earlier)
  3. Locate and inspect the tp_install function
    Access the plugin directory via file manager or FTP, open the main plugin PHP file, and search for the function named 'tp_install' to examine its code
    Affected if The tp_install function exists and performs plugin installation/activation without calling current_user_can() or a capability check
  4. Verify if the tp_install function lacks capability checks
    Within the tp_install function code, confirm there is no 'current_user_can' check, no 'manage_options' or similar capability requirement before executing plugin installation logic
    Affected if The function proceeds directly to install/activate plugins without verifying user permissions
  5. Test function accessibility (optional, requires caution)
    Review server access logs or test with a low-privilege unauthenticated request to the endpoint that triggers tp_install (commonly admin-post.php or a direct AJAX endpoint); do not actively exploit
    Affected if The function can be invoked without authentication and without a valid nonce or capability verification

If Vayu Blocks is installed with version 1.1.0 or earlier and the tp_install function lacks capability checks, the environment is vulnerable to unauthenticated plugin installation and potential remote code execution.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately update Vayu Blocks to the latest version and audit the site for any unauthorized plugins that may have been installed exploiting this vulnerability.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-10124 — 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-10124 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