CVE-2010-1340 json
Directory traversal vulnerability in jresearch.php in the J!Research (com_jresearch) component for Joomla!
published 16y ago modified 4mo ago also EUVD-2010-1368
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 13.6%
- EPSS 13.6% chance of exploitation in 30 days, percentile 96%
- public exploits
- 1
- Exploit-DB, plus a Nuclei check
Summary
Directory traversal vulnerability in jresearch.php in the J!Research (com_jresearch) component for Joomla! allows remote attackers to read arbitrary files via a .. (dot dot) in the controller parameter to index.php.
Is CVE-2010-1340 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-33797)
- Published
Exploit prediction
13.62% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-33797 Joomla! Component com_jresearch - 'Controller' Local File Inclusion webapps, 2010-03-24
- Nuclei template Joomla! Component com_jresearch - 'Controller' Local File Inclusion nuclei detection template
- securityfocus.com http://www.securityfocus.com/bid/38917 referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.org http://packetstormsecurity.org/1003-exploits/joomlajresearch-lfi.txt 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
-
securityfocus.com
/bid/38917
vdb-entry, exploit
-
packetstormsecurity.org
/1003-exploits/joomlajresearch-lfi.txt
exploit
-
secunia.com
/advisories/39079
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/57123
vdb-entry
-
osvdb.org
/63147
vdb-entry
Sources
- CVE List CVE-2010-1340
- NVD CVE-2010-1340
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.