CVE-2006-3050 json
Directory traversal vulnerability in detail.php in SixCMS 6.0, and other versions before 6.0.6patch2, allows remote attackers to read arbit…
published 2006-06-16 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-3047
- cvss
- 2.6
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.1%
- EPSS 3.1% chance of exploitation in 30 days, percentile 87%
- public exploits
- 1
- Exploit-DB
Summary
Directory traversal vulnerability in detail.php in SixCMS 6.0, and other versions before 6.0.6patch2, allows remote attackers to read arbitrary files via a .. (dot dot) sequence and trailing null (%00) byte in the template parameter.
Timeline
- First public exploit (EDB-28014)
- Published
Exploit prediction
3.11% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-28014 SixCMS 6.0 - 'detail.php' Directory Traversal webapps, 2006-06-12
- securityfocus.com http://www.securityfocus.com/bid/18395 referenced PoC, tagged "exploit" by a source, unverified
- majorsecurity.de http://www.majorsecurity.de/advisory/major_rls17.txt referenced PoC, tagged "exploit" by a source, unverified
- securitytracker.com http://securitytracker.com/id?1016282 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 2.6 | AV:N/AC:H/Au:N/C:P/I:N/A:N |
References
-
securityfocus.com
/bid/18395
vdb-entry, exploit
-
majorsecurity.de
/advisory/major_rls17.txt
exploit
-
securitytracker.com
/id?1016282
vdb-entry, exploit
-
exchange.xforce.ibmcloud.com
/vulnerabilities/27107
vdb-entry
-
securityfocus.com
/archive/1/437639/100/0/threaded
mailing-list
-
securityreason.com
/securityalert/1101
third-party-advisory
-
securityfocus.com
/archive/1/437047/100/0/threaded
mailing-list
Sources
- CVE List CVE-2006-3050
- NVD CVE-2006-3050
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.