CVE-2010-1353 json
Directory traversal vulnerability in the LoginBox Pro (com_loginbox) component for Joomla!
published 16y ago modified 4mo ago also EUVD-2010-1381
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 18.7%
- EPSS 18.7% chance of exploitation in 30 days, percentile 97%
- public exploits
- 1
- Exploit-DB, plus a Nuclei check
Summary
Directory traversal vulnerability in the LoginBox Pro (com_loginbox) component for Joomla! allows remote attackers to read arbitrary files via a .. (dot dot) in the view parameter to index.php.
Is CVE-2010-1353 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-12068)
- Published
Exploit prediction
18.70% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-12068 Joomla! Component LoginBox - Local File Inclusion webapps, 2010-04-05
- Nuclei template Joomla! Component LoginBox - Local File Inclusion nuclei detection template
- packetstormsecurity.org http://packetstormsecurity.org/1004-exploits/joomlaloginbox-lfi.txt referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/39212 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
-
exploit-db.com
/exploits/12068
exploit
-
packetstormsecurity.org
/1004-exploits/joomlaloginbox-lfi.txt
exploit
-
securityfocus.com
/bid/39212
vdb-entry, exploit
-
vupen.com
/english/advisories/2010/0808
vdb-entry, vendor-advisory
-
secunia.com
/advisories/39349
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/57533
vdb-entry
Sources
- CVE List CVE-2010-1353
- NVD CVE-2010-1353
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.