Path TraversalWeakness · CWE-22

CVE-2024-12885

MEDIUM · 6.5 CVSS v3.1 Published 2025-01-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/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 Connections Business Directory plugin for WordPress is vulnerable to arbitrary directory deletion due to insufficient file path validation when deleting a connections image directory in all versions up to, and including, 10.4.66. This makes it possible for authenticated attackers, with Administrator-level access and above, to delete arbitrary folders on the server and all their content.

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 Connections Business Directory WordPress plugin fails to validate file paths when processing directory deletion requests, allowing authenticated administrators to use path traversal sequences to delete arbitrary directories on the server. This occurs due to insufficient input sanitization on the connections image directory deletion functionality.

MitigationUpdate the Connections Business Directory plugin to version 10.4.67 or later. If immediate updating is not feasible, restrict administrator-level access or implement additional server-side access controls to mitigate the risk.

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/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. Verify Connections Business Directory plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Connections Business Directory'. Alternatively, check the /wp-content/plugins/connections directory exists.
    Affected if The plugin is installed and active
  2. Check the installed plugin version
    In WordPress admin, find the Connections Business Directory entry in the Plugins list and note the version number displayed. Compare it to the fixed version 10.4.67.
    Affected if Installed version is lower than 10.4.67 or version cannot be determined
  3. Confirm administrator role access exists
    Navigate to Users > All Users in WordPress admin and verify if any user accounts have the Administrator role assigned.
    Affected if At least one administrator-level user account exists on the site
  4. Check if image directory functionality is in use
    Review the plugin settings under Connections > Settings > Images, or inspect the database tables related to image directories (such as entry_images or similar) to see if any custom image paths have been configured.
    Affected if Custom image directories or paths are configured in the plugin

If the Connections Business Directory plugin is installed with a version below 10.4.67, has active administrator accounts, and uses custom image directory paths, the environment is affected by this path traversal vulnerability.

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 the Connections Business Directory plugin to version 10.4.67 or later. If immediate updating is not feasible, restrict administrator-level access or implement additional server-side access controls to mitigate the risk.

Recommended fix Moderate confidence

Connections Business Directory plugin version 10.4.67 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Connections Business Directory plugin
  4. Check if the current version is 10.4.66 or earlier
  5. If vulnerable, click 'Update Now' to install the latest version
  6. Alternatively, download the updated plugin from wordpress.org and upload via Plugins > Add New > Upload Plugin
  7. After update, verify the plugin version shows a version newer than 10.4.66

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-12885 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