CVE-2012-5907 json
Directory traversal vulnerability in json.php in TomatoCart 1.2.0 Alpha 2 and possibly earlier allows remote attackers to read arbitrary fi…
published 2012-11-17 13 y ago modified 2026-06-16 4 mo ago also EUVD-2012-5781
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 7.7%
- EPSS 7.7% chance of exploitation in 30 days, percentile 94%
- public exploits
- 1
- Exploit-DB
Summary
Directory traversal vulnerability in json.php in TomatoCart 1.2.0 Alpha 2 and possibly earlier allows remote attackers to read arbitrary files via a .. (dot dot) in the module parameter in a "3" action.
Timeline
- First public exploit (EDB-37021)
- Published
Exploit prediction
7.65% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-37021 TomatoCart 1.2.0 Alpha 2 - 'json.php' Local File Inclusion webapps, 2012-03-28
- securityfocus.com http://www.securityfocus.com/bid/52766 referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.org http://packetstormsecurity.org/files/111291/TomatoCart-1.2.0-Alpha-2-Local-File-Inclusion.html referenced PoC, tagged "exploit" by a source, unverified
- mavitunasecurity.com http://www.mavitunasecurity.com/local-file-inclusion-vulnerability-in-tomatocart/ 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
-
securityfocus.com
/bid/52766
vdb-entry, exploit
-
packetstormsecurity.org
/files/111291/TomatoCart-1.2.0-Alpha-2-Local-File-Inclusion.html
exploit
-
mavitunasecurity.com
/local-file-inclusion-vulnerability-in-tomatocart/
exploit
-
exchange.xforce.ibmcloud.com
/vulnerabilities/74459
vdb-entry
-
osvdb.org
/80689
vdb-entry
Sources
- CVE List CVE-2012-5907
- NVD CVE-2012-5907
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.