CVE-2006-2214
published 2006-05-05CVE-2006-2214: Multiple SQL injection vulnerabilities in 4images 1.7.1 and earlier allow remote attackers to execute arbitrary SQL commands via the sessionid parameter in (1)…
PriorityP340high7.5CVSS 2.0
AVNACLAuNCPIPAP
EXPLOIT
EPSS
2.67%
83.8th percentile
Multiple SQL injection vulnerabilities in 4images 1.7.1 and earlier allow remote attackers to execute arbitrary SQL commands via the sessionid parameter in (1) top.php and (2) member.php. NOTE: this issue has also been reported to affect 1.7.2.
Affected
2 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| 4images | image_gallery_management_system | <= 1.7.2 | — |
| 4images | image_gallery_management_system | — | — |
CVEs like this are exactly what “Exploited This Week” covers.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
No detection rules found.
Exploit-DB
4Images 1.7.1 - 'top.php?sessionid' SQL Injection
exploitdb·2006-04-29
CVE-2006-2214 4Images 1.7.1 - 'top.php?sessionid' SQL Injection
4Images 1.7.1 - 'top.php?sessionid' SQL Injection
---
source: https://www.securityfocus.com/bid/17748/info
4Images is prone to multiple, unspecified SQL-injection vulnerabilities. These issues are due to a failure in the application to properly sanitize user-supplied input before using it in an SQL query.
A successful exploit could allow an attacker to compromise the application, access or modify data, or exploit vulnerabilities in the underlying database implementation.
http://www.example.com/top.php?sessionid=[SQL]
Exploit-DB
4Images 1.7.1 - 'member.php?sessionid' SQL Injection
exploitdb·2006-04-29
CVE-2006-2214 4Images 1.7.1 - 'member.php?sessionid' SQL Injection
4Images 1.7.1 - 'member.php?sessionid' SQL Injection
---
source: https://www.securityfocus.com/bid/17748/info
4Images is prone to multiple, unspecified SQL-injection vulnerabilities. These issues are due to a failure in the application to properly sanitize user-supplied input before using it in an SQL query.
A successful exploit could allow an attacker to compromise the application, access or modify data, or exploit vulnerabilities in the underlying database implementation.
http://www.example.com/member.php?action=mailform&user_id=366&sessionid=[SQL]
http://archives.neohapsis.com/archives/bugtraq/2006-05/0012.htmlhttp://secunia.com/advisories/19908http://www.osvdb.org/25153http://www.osvdb.org/25154http://www.securityfocus.com/bid/17748http://www.vupen.com/english/advisories/2006/1604https://exchange.xforce.ibmcloud.com/vulnerabilities/26184http://archives.neohapsis.com/archives/bugtraq/2006-05/0012.htmlhttp://secunia.com/advisories/19908http://www.osvdb.org/25153http://www.osvdb.org/25154http://www.securityfocus.com/bid/17748http://www.vupen.com/english/advisories/2006/1604https://exchange.xforce.ibmcloud.com/vulnerabilities/26184
2006-05-05
Published