dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2024-13887

MEDIUM · 5.3 CVSS v3.1 Published 2025-03-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 Business Directory Plugin – Easy Listing Directories for WordPress plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 6.4.14 via the 'ajax_listing_submit_image_upload' function due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to add arbitrary images to listings.

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 Business Directory Plugin for WordPress contains an Insecure Direct Object Reference (IDOR) vulnerability in the ajax_listing_submit_image_upload function. The function fails to validate a user-controlled key, allowing unauthenticated attackers to add arbitrary images to any listing in the system without proper authorization.

MitigationUpdate the plugin to a version newer than 6.4.14 which contains the fix. If no patched version is available, consider disabling the plugin or implementing temporary firewall rules to block the vulnerable AJAX endpoint until a fix is released.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 Business Directory Plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder containing 'business-directory' or similar, or list installed plugins via WP-CLI: wp plugin list --status=active --format=csv
    Affected if The Business Directory Plugin appears in the installed plugins list
  2. Identify the installed plugin version
    Open the main plugin file (typically business-directory.php or class-business-directory-plugin.php) and look for the 'Version' header in the plugin comments, or run: grep -i 'Version:' wp-content/plugins/*business-directory*/README.txt 2>/dev/null
    Affected if The displayed version number is lower than 6.4.14 (e.g., 6.4.13, 6.4.10, 6.3.x, etc.)
  3. Confirm the vulnerable AJAX endpoint exists
    Test if the AJAX handler is accessible by making a request to wp-admin/admin-ajax.php with action=listing_submit_image_upload, or inspect the plugin source for the function ajax_listing_submit_image_upload
    Affected if The AJAX endpoint responds and the function exists in the plugin code without proper authorization checks
  4. Test unauthenticated image upload capability
    Send a crafted POST request to the AJAX endpoint with a listing ID parameter (the user-controlled key) and an image file, without providing authentication credentials
    Affected if The server accepts the upload and associates the image with a listing ID that differs from the attacker's own listing, confirming the IDOR vulnerability

A user is affected if the Business Directory Plugin is installed with a version lower than 6.4.14 and the ajax_listing_submit_image_upload AJAX endpoint permits unauthenticated image uploads to arbitrary listing IDs.

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 plugin to a version newer than 6.4.14 which contains the fix. If no patched version is available, consider disabling the plugin or implementing temporary firewall rules to block the vulnerable AJAX endpoint until a fix is released.

Recommended fix Moderate confidence

6.4.15 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'Business Directory Plugin – Easy Listing Directories for WordPress' plugin
  4. Click 'Update now' if an update is available, or manually update to version 6.4.15 or later
  5. Verify the update was successful by checking the plugin version
  6. Test that the listing image upload functionality works correctly for authenticated users

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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