CVE-2010-1722 json
Directory traversal vulnerability in the Online Market (com_market) component 2.x for Joomla!
published 16y ago modified 4mo ago also EUVD-2010-1742
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 9.5%
- EPSS 9.5% chance of exploitation in 30 days, percentile 95%
- public exploits
- 1
- Exploit-DB, plus a Nuclei check
Summary
Directory traversal vulnerability in the Online Market (com_market) component 2.x for Joomla! allows remote attackers to read arbitrary files and possibly have unspecified other impact via a .. (dot dot) in the controller parameter to index.php.
Is CVE-2010-1722 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-12177)
- Published
Exploit prediction
9.47% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-12177 Joomla! Component Online Market 2.x - Local File Inclusion webapps, 2010-04-12
- Nuclei template Joomla! Component Online Market 2.x - Local File Inclusion nuclei detection template
- packetstormsecurity.org http://packetstormsecurity.org/1004-exploits/joomlaonlinemarket-lfi.txt referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
exploit-db.com
/exploits/12177
exploit
-
packetstormsecurity.org
/1004-exploits/joomlaonlinemarket-lfi.txt
exploit
-
secunia.com
/advisories/39409
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/57674
vdb-entry
-
osvdb.org
/63671
vdb-entry
Sources
- CVE List CVE-2010-1722
- NVD CVE-2010-1722
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.