CVE-2005-4228 json
Multiple SQL injection vulnerabilities in PhpWebGallery 1.5.1 and earlier allow remote attackers to execute arbitrary SQL commands via the…
published 2005-12-14 20 y ago modified 2026-06-16 4 mo ago also EUVD-2005-4223
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.6%
- EPSS 2.6% chance of exploitation in 30 days, percentile 85%
- public exploits
- 3
- Exploit-DB
Summary
Multiple SQL injection vulnerabilities in PhpWebGallery 1.5.1 and earlier allow remote attackers to execute arbitrary SQL commands via the (1) since, (2) sort_by, and (3) items_number parameters to comments.php, (4) the search parameter to category.php, and (5) image_id parameter to picture.php. NOTE: it was later reported that the comments.php/sort_by vector also affects 1.7.2 and earlier.
Timeline
- First public exploit (EDB-26792)
- Published
Exploit prediction
2.56% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-26792 PHPWebGallery 1.3.4/1.5.1 - 'picture.php' SQL Injection webapps, 2005-12-13
- EDB-26791 PHPWebGallery 1.3.4/1.5.1 - 'category.php' SQL Injection webapps, 2005-12-13
- EDB-26790 PHPWebGallery 1.3.4/1.5.1 - 'comments.php' SQL Injection webapps, 2005-12-13
- securityfocus.com http://www.securityfocus.com/bid/15837 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
securityfocus.com
/bid/15837
vdb-entry, exploit
-
secunia.com
/advisories/18019
third-party-advisory, vendor-advisory
- pridels0.blogspot.com /2005/12/phpwebgallery-multiple-sql-inj.html
-
osvdb.org
/21690
vdb-entry
-
vupen.com
/english/advisories/2005/2881
vdb-entry
-
osvdb.org
/21691
vdb-entry
-
osvdb.org
/21689
vdb-entry
Sources
- CVE List CVE-2005-4228
- NVD CVE-2005-4228
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.