CVE-2010-1081 json
Directory traversal vulnerability in the Community Polls (com_communitypolls) component 1.5.2, and possibly earlier, for Core Joomla!
published 16y ago modified 4mo ago also EUVD-2010-1113
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 14.6%
- EPSS 14.6% chance of exploitation in 30 days, percentile 96%
- public exploits
- 1
- Exploit-DB, plus a Nuclei check
Summary
Directory traversal vulnerability in the Community Polls (com_communitypolls) component 1.5.2, and possibly earlier, for Core Joomla! allows remote attackers to read arbitrary files via a .. (dot dot) in the controller parameter to index.php.
Is CVE-2010-1081 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-11511)
- Published
Exploit prediction
14.60% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-11511 Joomla! Component com_communitypolls 1.5.2 - Local File Inclusion webapps, 2010-02-19
- Nuclei template Joomla! Component com_communitypolls 1.5.2 - Local File Inclusion nuclei detection template
- packetstormsecurity.org http://packetstormsecurity.org/1002-exploits/joomlacp-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
-
packetstormsecurity.org
/1002-exploits/joomlacp-lfi.txt
exploit
-
secunia.com
/advisories/38692
third-party-advisory, vendor-advisory
-
corejoomla.com
/component/content/article/1-corejoomla-updates/40-community-polls-v153-security-release.html
vendor-advisory
-
securityfocus.com
/bid/38330
vdb-entry
-
osvdb.org
/62506
vdb-entry
Sources
- CVE List CVE-2010-1081
- NVD CVE-2010-1081
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.