CVE-2024-13538 json
BigBuy Dropshipping Connector for WooCommerce <= 2.0.0 - Unauthenticated Full Path Disclosute
published 2025-02-18 20 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-4847
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 50%
- public exploits
- 0
- none known
Summary
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.
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 20 mo ago
Exploit prediction
0.62% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected products
- devsmip BigBuy Dropshipping Connector for WooCommerce
Classification
- Weakness
- Technology feeds
References
-
wordfence.com
/threat-intel/vulnerabilities/id/15f38b3e-69fe-436f-ba4b-7985ec9dac00?source=cve
third-party-advisory
-
plugins.trac.wordpress.org
/browser/bigbuy-wc-dropshipping-connector/trunk/vendor/cocur/slugify/bin/generate-default.php
product
- plugins.trac.wordpress.org /changeset?sfp_email=&sfph_mail=&reponame=&old=3281936%40bigbuy-wc-dropshipping-connector&new=3281936%40bigbuy
- plugins.trac.wordpress.org /browser/bigbuy-wc-dropshipping-connector/tags/2.0.0/vendor/cocur/slugify/bin/generate-default.php
Sources
- CVE List CVE-2024-13538
- NVD CVE-2024-13538
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.