CVE-2010-0943 json
Directory traversal vulnerability in the JA Showcase (com_jashowcase) component for Joomla!
published 16y ago modified 4mo ago also EUVD-2010-0968
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 15.9%
- EPSS 15.9% chance of exploitation in 30 days, percentile 96%
- public exploits
- 1
- Exploit-DB, plus a Nuclei check
Summary
Directory traversal vulnerability in the JA Showcase (com_jashowcase) component for Joomla! allows remote attackers to read arbitrary files via a .. (dot dot) in the controller parameter in a jashowcase action to index.php.
Is CVE-2010-0943 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-11090)
- Published
Exploit prediction
15.94% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-11090 Joomla! Component com_jashowcase - Directory Traversal webapps, 2010-01-10
- Nuclei template Joomla! Component com_jashowcase - Directory Traversal nuclei detection template
- securityfocus.com http://www.securityfocus.com/bid/37692 referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.org http://packetstormsecurity.org/1001-exploits/joomlajashowcase-traversal.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
-
exploit-db.com
/exploits/11090
exploit
-
securityfocus.com
/bid/37692
vdb-entry, exploit
-
packetstormsecurity.org
/1001-exploits/joomlajashowcase-traversal.txt
exploit
-
secunia.com
/advisories/33486
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/55512
vdb-entry
Sources
- CVE List CVE-2010-0943
- NVD CVE-2010-0943
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.