CVE-2010-1954 in the critical feed json
Directory traversal vulnerability in the iNetLanka Multiple root (com_multiroot) component 1.0 and 1.1 for Joomla!
published 16y ago modified 4mo ago also EUVD-2010-1973
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 16.2%
- EPSS 16.2% chance of exploitation in 30 days, percentile 96%
- public exploits
- 1
- Exploit-DB, plus a Nuclei check
Summary
Directory traversal vulnerability in the iNetLanka Multiple root (com_multiroot) component 1.0 and 1.1 for Joomla! allows remote attackers to read arbitrary files via a .. (dot dot) in the controller parameter to index.php. NOTE: some of these details are obtained from third party information.
Is CVE-2010-1954 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-12287)
- Published
Exploit prediction
16.15% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-12287 Joomla! Component iNetLanka Multiple root 1.0 - Local File Inclusion webapps, 2010-04-18
- Nuclei template Joomla! Component iNetLanka Multiple root 1.0 - Local File Inclusion nuclei detection template
- securityfocus.com http://www.securityfocus.com/bid/39552 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/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/12287
exploit
-
securityfocus.com
/bid/39552
vdb-entry, exploit
-
vupen.com
/english/advisories/2010/0928
vdb-entry, vendor-advisory
-
secunia.com
/advisories/39531
third-party-advisory, vendor-advisory
Sources
- CVE List CVE-2010-1954
- NVD CVE-2010-1954
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.