CVE-2010-3456 json
Directory traversal vulnerability in download.php in EnergyScripts (ES) Simple Download 1.0 allows remote attackers to read arbitrary files…
published 16y ago modified 4mo ago also EUVD-2010-3454
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 7.6%
- EPSS 7.6% chance of exploitation in 30 days, percentile 94%
- public exploits
- 1
- Exploit-DB
Summary
Directory traversal vulnerability in download.php in EnergyScripts (ES) Simple Download 1.0 allows remote attackers to read arbitrary files via a .. (dot dot) in the file parameter.
Is CVE-2010-3456 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-14960)
- Published
Exploit prediction
7.61% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-14960 ES Simple Download 1.0. - Local File Inclusion webapps, 2010-09-09
- securityfocus.com http://www.securityfocus.com/bid/43124 referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.org http://packetstormsecurity.org/1009-exploits/essimpledownload-lfi.txt 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
References
-
exploit-db.com
/exploits/14960
exploit
-
securityfocus.com
/bid/43124
vdb-entry, exploit
-
packetstormsecurity.org
/1009-exploits/essimpledownload-lfi.txt
exploit
-
secunia.com
/advisories/41359
third-party-advisory, vendor-advisory
-
osvdb.org
/67944
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/61718
vdb-entry
Sources
- CVE List CVE-2010-3456
- NVD CVE-2010-3456
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.