CVE-2010-2033 in the critical feed json
Directory traversal vulnerability in the Percha Multicategory Article (com_perchacategoriestree) component 0.6 for Joomla!
published 2010-05-25 16 y ago modified 2026-06-16 4 mo ago also EUVD-2010-2053
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 15.8%
- EPSS 15.8% chance of exploitation in 30 days, percentile 96%
- public exploits
- 1
- Exploit-DB, plus a Nuclei check
Summary
Directory traversal vulnerability in the Percha Multicategory Article (com_perchacategoriestree) component 0.6 for Joomla! allows remote attackers to read arbitrary files and possibly have unspecified other impact via a .. (dot dot) in the controller parameter to index.php.
Timeline
- First public exploit (EDB-34008)
- Published
Exploit prediction
15.79% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-34008 Joomla! Component Percha Multicategory Article 0.6 - 'Controller' Arbitrary File Access webapps, 2010-05-19
- Nuclei template Joomla! Percha Categories Tree 0.6 - Local File Inclusion nuclei detection template
- packetstormsecurity.org http://packetstormsecurity.org/1005-exploits/joomlaperchact-lfi.txt referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/40244 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
-
packetstormsecurity.org
/1005-exploits/joomlaperchact-lfi.txt
exploit
-
securityfocus.com
/bid/40244
vdb-entry, exploit
-
secunia.com
/advisories/39873
third-party-advisory, vendor-advisory
Sources
- CVE List CVE-2010-2033
- NVD CVE-2010-2033
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.