CVE-2013-7240 json
Directory traversal vulnerability in download-file.php in the Advanced Dewplayer plugin 1.2 for WordPress allows remote attackers to read a…
published 12y ago modified 4mo ago also EUVD-2013-7019
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 19.6%
- EPSS 19.6% chance of exploitation in 30 days, percentile 97%
- public exploits
- 1
- Exploit-DB, plus a Nuclei check
Summary
Directory traversal vulnerability in download-file.php in the Advanced Dewplayer plugin 1.2 for WordPress allows remote attackers to read arbitrary files via a .. (dot dot) in the dew_file parameter.
Is CVE-2013-7240 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (EDB-38936)
- Published
Exploit prediction
19.64% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-38936 WordPress Plugin Advanced Dewplayer - 'download-file.php' Script Directory Traversal webapps, 2013-12-30
- Nuclei template WordPress Plugin Advanced Dewplayer 1.2 - Directory Traversal nuclei detection template
- securityfocus.com http://www.securityfocus.com/bid/64587 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/64587
vdb-entry, exploit
-
wordpress.org
/support/topic/security-vulnerability-cve-2013-7240-directory-traversal
vendor-advisory
-
seclists.org
/oss-sec/2013/q4/570
mailing-list
-
seclists.org
/oss-sec/2013/q4/566
mailing-list
Sources
- CVE List CVE-2013-7240
- NVD CVE-2013-7240
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.