Skip to content
Fencer Intel
high 7.5

CVE-2010-1956 in the critical feed json

Directory traversal vulnerability in the Gadget Factory (com_gadgetfactory) component 1.0.0 and 1.5.0 for Joomla!

published 16y ago modified 4mo ago also EUVD-2010-1975

cvss
7.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
17.0%
EPSS 17.0% chance of exploitation in 30 days, percentile 97%
public exploits
1
Exploit-DB, plus a Nuclei check

Summary

Directory traversal vulnerability in the Gadget Factory (com_gadgetfactory) component 1.0.0 and 1.5.0 for Joomla! allows remote attackers to read arbitrary files via a .. (dot dot) in the controller parameter to index.php. NOTE: some of these details are obtained from third party information.

Patch / fix

Is CVE-2010-1956 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 Fencer

Timeline

  1. First public exploit (EDB-12285)
  2. Published

Exploit prediction

17.00% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-12285 Joomla! Component Gadget Factory 1.0.0 - Local File Inclusion webapps, 2010-04-18
  • Nuclei template Joomla! Component Gadget Factory 1.0.0 - Local File Inclusion nuclei detection template
  • securityfocus.com http://www.securityfocus.com/bid/39547 referenced PoC, tagged "exploit" by a source, unverified
  • osvdb.org http://osvdb.org/63917 referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.org http://packetstormsecurity.org/1004-exploits/joomlagadgetfactory-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

Sources

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.