CVE-2005-2256 json
Encoded directory traversal vulnerability in phpPgAdmin 3.1 to 3.5.3 allows remote attackers to access arbitrary files via "%2e%2e%2f" (enc…
published 2005-07-13 21 y ago modified 2026-06-16 4 mo ago also EUVD-2005-2257
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.6%
- EPSS 4.6% chance of exploitation in 30 days, percentile 91%
- public exploits
- 1
- Exploit-DB
Summary
Encoded directory traversal vulnerability in phpPgAdmin 3.1 to 3.5.3 allows remote attackers to access arbitrary files via "%2e%2e%2f" (encoded dot dot) sequences in the formLanguage parameter.
Patch / fix
- phppgadmin Debian 14, Debian 13 3.5.4-1
debian advisories DEBIAN-CVE-2005-2256
Timeline
- First public exploit (EDB-25938)
- Published
Exploit prediction
4.64% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-25938 phpPgAdmin 3.x - Login Form Directory Traversal webapps, 2005-07-05
- securityfocus.com http://www.securityfocus.com/bid/14142 referenced PoC, tagged "exploit" by a source, unverified
- securitytracker.com http://securitytracker.com/id?1014414 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/14142
vdb-entry, exploit
-
securitytracker.com
/id?1014414
vdb-entry, exploit
-
debian.org
/security/2005/dsa-759
vendor-advisory
-
vuxml.org
/freebsd/88188a8c-eff6-11d9-8310-0001020eed82.html
vendor-advisory
-
secunia.com
/advisories/15941
third-party-advisory, vendor-advisory
-
archives.neohapsis.com
/archives/dailydave/2005-q3/0010.html
mailing-list
-
secunia.com
/advisories/16116
third-party-advisory
- sourceforge.net /project/shownotes.php?release_id=342261
Sources
- CVE List CVE-2005-2256
- NVD CVE-2005-2256
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.