CVE-2010-4801 json
Directory traversal vulnerability in admin/updatelist.php in BaconMap 1.0 allows remote attackers to include and execute arbitrary local fi…
published 2011-04-27 15 y ago modified 2026-06-16 4 mo ago also EUVD-2010-4766
- cvss
- 6.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.0%
- EPSS 2.0% chance of exploitation in 30 days, percentile 80%
- public exploits
- 1
- Exploit-DB
Summary
Directory traversal vulnerability in admin/updatelist.php in BaconMap 1.0 allows remote attackers to include and execute arbitrary local files via a .. (dot dot) in the filepath parameter.
Timeline
- First public exploit (EDB-15234)
- Published
Exploit prediction
2.00% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-15234 BaconMap 1.0 - Local File Disclosure webapps, 2010-10-11
- securityfocus.com http://www.securityfocus.com/bid/43908 referenced PoC, tagged "exploit" by a source, unverified
- johnleitch.net http://www.johnleitch.net/Vulnerabilities/BaconMap.1.0.Local.File.Inclusion/50 referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.org http://packetstormsecurity.org/1010-exploits/baconmap10-lfi.txt referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.0 | AV:N/AC:M/Au:S/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
exploit-db.com
/exploits/15234
exploit
-
securityfocus.com
/bid/43908
vdb-entry, exploit
-
johnleitch.net
/Vulnerabilities/BaconMap.1.0.Local.File.Inclusion/50
exploit
-
packetstormsecurity.org
/1010-exploits/baconmap10-lfi.txt
exploit
-
secunia.com
/advisories/41749
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/62390
vdb-entry
-
securityreason.com
/securityalert/8229
third-party-advisory
Sources
- CVE List CVE-2010-4801
- NVD CVE-2010-4801
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.