dbcve.org
Dropshipping Connector For WoocommerceWordPress extension · Bigbuy

CVE-2024-13538

MEDIUM · 5.3 CVSS v3.1 Published 2025-02-18
Fix available
A fix is available. Upgrade to after 1.9.19 or later.
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 BigBuy Dropshipping Connector for WooCommerce plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 2.0.0. This is due the /vendor/cocur/slugify/bin/generate-default.php file being directly accessible and triggering an error. This makes it possible for unauthenticated attackers to retrieve the full path of the web application, which can be used to aid other attacks. The information displayed is not useful on its own, and requires another vulnerability to be present for damage to an affected website.

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 BigBuy Dropshipping Connector plugin for WordPress is vulnerable to Full Path Disclosure (FPD) due to the directly accessible file /vendor/cocur/slugify/bin/generate-default.php. This file is part of a third-party dependency (cocur/slugify) and when accessed directly via web, it triggers an error that reveals the absolute server path of the WordPress installation. Unauthenticated attackers can exploit this to discover the full filesystem path, which aids in crafting further attacks such as path traversal or local file inclusion exploits.

MitigationBlock direct web access to PHP files in the /vendor/ directory using .htaccess rules (Apache) or location blocks in nginx configuration, or update the plugin to a patched version if available.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Dropshipping Connector For WoocommerceWordPress extension
Affected:<= 1.9.19

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Confirm plugin is installed
    Navigate to WordPress admin > Plugins and verify 'Bigbuy Dropshipping Connector For Woocommerce' is installed and active
    Affected if Plugin is installed and active
  2. Check installed plugin version
    In WordPress admin > Plugins, click on the plugin details to view the installed version number
    Affected if Version is 1.9.19 or lower (any version <= 1.9.19)
  3. Verify vulnerable file exists
    Check if the file /wp-content/plugins/bigbuy-drop-shipping-connector-for-woocommerce/vendor/cocur/slugify/bin/generate-default.php exists on the server filesystem
    Affected if File exists in the plugin directory
  4. Test web access to vulnerable file
    Using a web browser or curl, attempt to access the URL: https://yourdomain.com/wp-content/plugins/bigbuy-drop-shipping-connector-for-woocommerce/vendor/cocur/slugify/bin/generate-default.php
    Affected if Request returns an error message that includes the absolute server filesystem path (e.g., /home/username/public_html/)

User is affected if the Bigbuy Dropshipping Connector plugin version is <= 1.9.19 AND the vulnerable PHP file is directly accessible via web and reveals the absolute server path when accessed.

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
Upgrade available Upgrade to a release after 1.9.19
Interim mitigation

Block direct web access to PHP files in the /vendor/ directory using .htaccess rules (Apache) or location blocks in nginx configuration, or update the plugin to a patched version if available.

Recommended fix Moderate confidence

Upgrade to the latest available version (likely 2.0.1 or higher)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'BigBuy Dropshipping Connector for WooCommerce' (or 'Dropshipping Connector For Woocommerce')
  4. Check the current version installed
  5. If the current version is <= 1.9.19 (or <= 2.0.0), click 'Update now' if an update is available
  6. Alternatively, download the latest version from the WordPress plugin repository and upload it manually via Plugins > Add New > Upload Plugin
  7. After updating, verify the /vendor/cocur/slugify/bin/generate-default.php file is no longer directly accessible

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

Fix this in Dropshipping Connector For Woocommerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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