dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-9860

MEDIUM · 5.4 CVSS v3.1 Published 2024-10-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
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 Bridge Core plugin for WordPress is vulnerable to unauthorized modification of data or loss of data due to a missing capability check on the 'import_action' and 'install_plugin_per_demo' functions in versions up to, and including, 3.3. This makes it possible for authenticated attackers with subscriber-level permissions or above, to delete or change plugin settings, import demo data, and install limited plugins.

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 Bridge Core WordPress plugin versions up to 3.3 lack proper capability checks on the 'import_action' and 'install_plugin_per_demo' functions, allowing any authenticated user with subscriber-level permissions or higher to execute these privileged functions. This broken access control vulnerability enables attackers to modify plugin settings, import demo data, and install limited plugins without proper authorization.

MitigationApply the vendor patch (version 3.4 or higher) which adds required capability checks to the vulnerable functions. Until patched, consider restricting user registration or monitoring for suspicious activity.

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
None
Integrity
Low
Availability
Low

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

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 Bridge Core plugin is installed
    Navigate to WordPress admin Dashboard > Plugins > Installed Plugins and look for 'Bridge Core' in the list, or check for the /wp-content/plugins/bridge-core/ directory on the server file system.
    Affected if The Bridge Core plugin is not found in the WordPress installation.
  2. Identify installed Bridge Core version
    In WordPress admin, locate Bridge Core in the Plugins list and read the version number from the plugin row. Alternatively, open the main plugin file (typically /wp-content/plugins/bridge-core/bridge-core.php) and look for the 'Version' header comment at the top of the file.
    Affected if The installed version is 3.3 or lower (versions up to and including 3.3 are affected).
  3. Verify AJAX action handlers exist
    Search the plugin files for the strings 'import_action' and 'install_plugin_per_demo' to confirm these AJAX callback functions exist in the codebase. Check files in the /wp-content/plugins/bridge-core/ directory, particularly any PHP files handling AJAX requests.
    Affected if These function names are found in the plugin code, indicating the vulnerable functions are present.
  4. Check for missing capability checks
    Examine the PHP code handling the AJAX actions (look for add_action calls with 'wp_ajax_import_action' and 'wp_ajax_nopriv_import_action' or similar). Verify whether the callback functions include current_user_can() or a capability check before performing privileged operations.
    Affected if The AJAX handlers either lack capability checks entirely or only check for any authenticated user (subscriber level) rather than an administrator-level capability.

You are affected if the Bridge Core plugin is installed with version 3.3 or lower and the import_action and install_plugin_per_demo functions are accessible to users with subscriber-level permissions without proper capability validation.

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

Apply the vendor patch (version 3.4 or higher) which adds required capability checks to the vulnerable functions. Until patched, consider restricting user registration or monitoring for suspicious activity.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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