CVE-2005-4880 json
Jax Guestbook 3.1 and 3.31 stores sensitive information under the web root with insufficient access control, which allows remote attackers…
published 2009-03-31 17 y ago modified 2026-06-16 4 mo ago also EUVD-2005-4871
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.4%
- EPSS 2.4% chance of exploitation in 30 days, percentile 84%
- public exploits
- 4
- Exploit-DB
Summary
Jax Guestbook 3.1 and 3.31 stores sensitive information under the web root with insufficient access control, which allows remote attackers to obtain IP addresses of users via a direct request to (1) guestbook, (2) guestbook_ips2block, (3) ips2block, and (4) formmailer/logfile.csv.
Timeline
- First public exploit (EDB-26092)
- Published
Exploit prediction
2.39% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-26092 Jax PHP Scripts 1.0/1.34/2.14/3.31 - logfile.csv User IP Disclosure webapps, 2005-08-05
- EDB-26091 Jax PHP Scripts 1.0/1.34/2.14/3.31 - ips2block Banned IP List Disclosure webapps, 2005-08-05
- EDB-26090 Jax PHP Scripts 1.0/1.34/2.14/3.31 - guestbook_ips2block Banned IP List Disclosure webapps, 2005-08-05
- EDB-26089 Jax PHP Scripts 1.0/1.34/2.14/3.31 - Guestbook File Client IP Disclosure webapps, 2005-08-05
- lostmon.blogspot.com http://lostmon.blogspot.com/2005/08/jax-php-scripts-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-264 Permissions, Privileges, and Access Controls
References
-
lostmon.blogspot.com
/2005/08/jax-php-scripts-multiple.html
exploit
-
secunia.com
/advisories/16337
third-party-advisory, vendor-advisory
Sources
- CVE List CVE-2005-4880
- NVD CVE-2005-4880
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.