CVE-2010-3426 in the critical feed json
Directory traversal vulnerability in jphone.php in the JPhone (com_jphone) component 1.0 Alpha 3 for Joomla!
published 16y ago modified 4mo ago also EUVD-2010-3424
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 13.9%
- EPSS 13.9% chance of exploitation in 30 days, percentile 96%
- public exploits
- 1
- Exploit-DB, plus a Nuclei check
Summary
Directory traversal vulnerability in jphone.php in the JPhone (com_jphone) component 1.0 Alpha 3 for Joomla! allows remote attackers to include and execute arbitrary local files via a .. (dot dot) in the controller parameter to index.php.
Is CVE-2010-3426 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-14964)
- Published
Exploit prediction
13.85% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-14964 Joomla! Component Jphone 1.0 Alpha 3 - Local File Inclusion webapps, 2010-09-10
- Nuclei template Joomla! Component Jphone 1.0 Alpha 3 - Local File Inclusion nuclei detection template
- securityfocus.com http://www.securityfocus.com/bid/43147 referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.org http://packetstormsecurity.org/1009-exploits/joomlajphone-lfi.txt 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/14964
exploit
-
securityfocus.com
/bid/43147
vdb-entry, exploit
-
packetstormsecurity.org
/1009-exploits/joomlajphone-lfi.txt
exploit
-
exchange.xforce.ibmcloud.com
/vulnerabilities/61723
vdb-entry
Sources
- CVE List CVE-2010-3426
- NVD CVE-2010-3426
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.