CVE-2009-4088 json
Multiple directory traversal vulnerabilities in telepark.wiki 2.4.23 and earlier allow remote attackers to read arbitrary files via directo…
published 2009-11-27 16 y ago modified 2026-06-16 4 mo ago also EUVD-2009-4059
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.8%
- EPSS 2.8% chance of exploitation in 30 days, percentile 86%
- public exploits
- 2
- Exploit-DB
Summary
Multiple directory traversal vulnerabilities in telepark.wiki 2.4.23 and earlier allow remote attackers to read arbitrary files via directory traversal sequences in the css parameter to (1) getjs.php and (2) getcsslocal.php; and include and execute arbitrary local files via the (3) group parameter to upload.php.
Patch / fix
Timeline
- First public exploit (EDB-9483)
- Published
Exploit prediction
2.80% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-10101 telepark wiki 2.4.23 - Multiple Vulnerabilities webapps, 2009-11-16
- EDB-9483 Photodex ProShow Gold 4 (Windows XP SP3) - '.psh' Universal Buffer Overflow (SEH) local, 2009-08-24
- packetstormsecurity.org http://packetstormsecurity.org/0911-exploits/Telepark-fixes-nov09-2.txt 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
-
blog.telepark.com
/telepark-web-software/2009/11/09/telepark-wiki-security-fixes/
patch
-
exploit-db.com
/exploits/9483
exploit
-
packetstormsecurity.org
/0911-exploits/Telepark-fixes-nov09-2.txt
exploit
-
secunia.com
/advisories/37391
third-party-advisory, vendor-advisory
-
osvdb.org
/60218
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/54327
vdb-entry
-
osvdb.org
/60216
vdb-entry
-
osvdb.org
/60217
vdb-entry
Sources
- CVE List CVE-2009-4088
- NVD CVE-2009-4088
Fencer Vulns 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.