CVE-2014-5368 json
Directory traversal vulnerability in the file_get_contents function in downloadfiles/download.php in the WP Content Source Control (wp-sour…
published 2014-08-22 12 y ago modified 2026-06-17 4 mo ago also EUVD-2014-5256
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 18.8%
- EPSS 18.8% chance of exploitation in 30 days, percentile 97%
- public exploits
- 1
- Exploit-DB, plus a Nuclei check
Summary
Directory traversal vulnerability in the file_get_contents function in downloadfiles/download.php in the WP Content Source Control (wp-source-control) plugin 3.0.0 and earlier for WordPress allows remote attackers to read arbitrary files via a .. (dot dot) in the path parameter.
Timeline
- First public exploit (EDB-39287)
- Published
Exploit prediction
18.82% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-39287 WordPress Plugin WP Content Source Control - 'download.php' Directory Traversal webapps, 2014-08-19
- Nuclei template WordPress Plugin WP Content Source Control - Directory Traversal nuclei detection template
- securityfocus.com http://www.securityfocus.com/bid/69278 referenced PoC, tagged "exploit" by a source, unverified
- seclists.org http://seclists.org/oss-sec/2014/q3/417 referenced PoC, tagged "exploit" by a source, unverified
- seclists.org http://seclists.org/oss-sec/2014/q3/407 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
- Technology feeds
References
-
securityfocus.com
/bid/69278
vdb-entry, exploit
-
seclists.org
/oss-sec/2014/q3/417
mailing-list, exploit
-
seclists.org
/oss-sec/2014/q3/407
mailing-list, exploit
-
exchange.xforce.ibmcloud.com
/vulnerabilities/95374
vdb-entry
Sources
- CVE List CVE-2014-5368
- NVD CVE-2014-5368
Fencer Intel 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.