CVE-2006-1995 json
Directory traversal vulnerability in index.php in Scry Gallery 1.1 allows remote attackers to read arbitrary files via ".." sequences in th…
published 2006-04-25 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-1995
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.5%
- EPSS 4.5% chance of exploitation in 30 days, percentile 91%
- public exploits
- 1
- Exploit-DB
Summary
Directory traversal vulnerability in index.php in Scry Gallery 1.1 allows remote attackers to read arbitrary files via ".." sequences in the p parameter, which is not properly sanitized due to an rtrim function call with the arguments in the wrong order.
Timeline
- First public exploit (EDB-27724)
- Published
Exploit prediction
4.48% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-27724 Scry Gallery - Directory Traversal webapps, 2006-04-21
- securityfocus.com http://www.securityfocus.com/bid/17649 referenced PoC, tagged "exploit" by a source, unverified
- downloads.securityfocus.com http://downloads.securityfocus.com/vulnerabilities/exploits/17649-directory-traversal.exploit 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
-
securityfocus.com
/bid/17649
vdb-entry, exploit
-
downloads.securityfocus.com
/vulnerabilities/exploits/17649-directory-traversal.exploit
exploit
-
securityfocus.com
/bid/17668
vdb-entry
-
vupen.com
/english/advisories/2006/1490
vdb-entry
-
osvdb.org
/24889
vdb-entry
-
securityreason.com
/securityalert/784
third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/25991
vdb-entry
-
attrition.org
/pipermail/vim/2006-April/000716.html
mailing-list
-
securityfocus.com
/archive/1/431716/100/0/threaded
mailing-list
-
secunia.com
/advisories/19777
third-party-advisory
Sources
- CVE List CVE-2006-1995
- NVD CVE-2006-1995
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.