CVE-2009-2007 json
Multiple directory traversal vulnerabilities in Dokeos 1.8.5, and possibly earlier, allow remote attackers to (1) read portions of arbitrar…
published 2009-06-08 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-2003
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.9%
- EPSS 1.9% chance of exploitation in 30 days, percentile 80%
- public exploits
- 0
- none known
Summary
Multiple directory traversal vulnerabilities in Dokeos 1.8.5, and possibly earlier, allow remote attackers to (1) read portions of arbitrary files via a .. (dot dot) and a ..\ (dot dot backslash) in the lang parameter to main/exercice/hotspot_lang_conversion.php and (2) read arbitrary files via a .. (dot dot) in the doc_url parameter to main/exercice/Hpdownload.php.
Patch / fix
Exploit prediction
1.93% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- dokeos.com http://www.dokeos.com/wiki/index.php/Security#Dokeos_1.8 referenced PoC, tagged "exploit" by a source, unverified
- gsasec.blogspot.com http://gsasec.blogspot.com/2009/05/dokeos-free-185-multiple.html 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
-
vupen.com
/english/advisories/2009/1300
vdb-entry, patch, vendor-advisory
-
dokeos.com
/wiki/index.php/Security#Dokeos_1.8
exploit, patch
-
gsasec.blogspot.com
/2009/05/dokeos-free-185-multiple.html
exploit
-
secunia.com
/advisories/34879
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/50503
vdb-entry
-
securityfocus.com
/bid/34928
vdb-entry
Sources
- CVE List CVE-2009-2007
- NVD CVE-2009-2007
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.