CVE-2006-5125 json
Directory traversal vulnerability in window.php, possibly used by home.php, in Joshua Muheim phpMyWebmin 1.0 allows remote attackers to obt…
published 2006-10-02 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-5110
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.7%
- EPSS 3.7% chance of exploitation in 30 days, percentile 89%
- public exploits
- 2
- Exploit-DB
Summary
Directory traversal vulnerability in window.php, possibly used by home.php, in Joshua Muheim phpMyWebmin 1.0 allows remote attackers to obtain sensitive information via a directory name in the target parameter, which triggers a directory listing through the opendir function.
Timeline
- First public exploit (EDB-2451)
- Published
Exploit prediction
3.73% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-2462 phpMyWebmin 1.0 - 'target' Remote File Inclusion webapps, 2006-09-30
- EDB-2451 phpMyWebmin 1.0 - 'window.php' Remote File Inclusion webapps, 2006-09-28
- securityfocus.com http://www.securityfocus.com/bid/20264 referenced PoC, tagged "exploit" by a source, unverified
- kernel-32.blogspot.com http://kernel-32.blogspot.com/2006/09/php-mywebmin-10-remote-file-include.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 |
References
-
exploit-db.com
/exploits/2451
exploit
-
securityfocus.com
/bid/20264
vdb-entry, exploit
-
kernel-32.blogspot.com
/2006/09/php-mywebmin-10-remote-file-include.html
exploit
-
secunia.com
/advisories/22178
third-party-advisory, vendor-advisory
-
vupen.com
/english/advisories/2006/3846
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/29259
vdb-entry
Sources
- CVE List CVE-2006-5125
- NVD CVE-2006-5125
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.