CVE-2010-1469 json
Directory traversal vulnerability in the Ternaria Informatica JProject Manager (com_jprojectmanager) component 1.0 for Joomla!
published 16y ago modified 4mo ago also EUVD-2010-1496
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 8.2%
- EPSS 8.2% chance of exploitation in 30 days, percentile 94%
- public exploits
- 1
- Exploit-DB, plus a Nuclei check
Summary
Directory traversal vulnerability in the Ternaria Informatica JProject Manager (com_jprojectmanager) component 1.0 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-1469 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-12146)
- Published
Exploit prediction
8.16% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-12146 Joomla! Component JProject Manager 1.0 - Local File Inclusion webapps, 2010-04-11
- Nuclei template Joomla! Component JProject Manager 1.0 - Local File Inclusion nuclei detection template
- securityfocus.com http://www.securityfocus.com/bid/39383 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/12146
exploit
-
securityfocus.com
/bid/39383
vdb-entry, exploit
-
secunia.com
/advisories/39282
third-party-advisory, vendor-advisory
- packetstormsecurity.org /1004-exploits/joomlajprojectmanager-lfi.txt
Sources
- CVE List CVE-2010-1469
- NVD CVE-2010-1469
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.