CVE-2009-4426 json
Multiple directory traversal vulnerabilities in Ignition 1.2, when magic_quotes_gpc is disabled, allow remote attackers to include and exec…
published 16y ago modified 4mo ago also EUVD-2009-4393
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.3%
- EPSS 2.3% chance of exploitation in 30 days, percentile 83%
- public exploits
- 1
- Exploit-DB
Summary
Multiple directory traversal vulnerabilities in Ignition 1.2, when magic_quotes_gpc is disabled, allow remote attackers to include and execute arbitrary local files via a .. (dot dot) in the blog parameter to (1) comment.php and (2) view.php.
Is CVE-2009-4426 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-10569)
- Published
Exploit prediction
2.35% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-10569 Ignition 1.2 - Multiple Local File Inclusions webapps, 2009-12-20
- packetstormsecurity.org http://packetstormsecurity.org/0912-exploits/ignition-lfi.txt referenced PoC, tagged "exploit" by a source, unverified
- osvdb.org http://osvdb.org/61226 referenced PoC, tagged "exploit" by a source, unverified
- osvdb.org http://osvdb.org/61225 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
exploit-db.com
/exploits/10569
exploit
-
packetstormsecurity.org
/0912-exploits/ignition-lfi.txt
exploit
-
osvdb.org
/61226
vdb-entry, exploit
-
osvdb.org
/61225
vdb-entry, exploit
-
secunia.com
/advisories/37836
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/54940
vdb-entry
Sources
- CVE List CVE-2009-4426
- NVD CVE-2009-4426
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.