CVE-2005-4001
published 2005-12-05CVE-2005-4001: Multiple SQL injection vulnerabilities in phpYellowTM Pro Edition and Lite Edition 5.33 allow remote attackers to execute arbitrary SQL commands via the (1)…
PriorityP338high7.5CVSS 2.0
AVNACLAuNCPIPAP
EXPLOIT
EPSS
1.29%
66.6th percentile
Multiple SQL injection vulnerabilities in phpYellowTM Pro Edition and Lite Edition 5.33 allow remote attackers to execute arbitrary SQL commands via the (1) haystack parameter to search_result.php or (2) ckey parameter to print_me.php.
Affected
2 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| phpyellow | phpyellowtm_lite | — | — |
| phpyellow | phpyellowtm_pro | — | — |
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
PHPYellowTM 5.33 - 'search_result.php?haystack' SQL Injection
exploitdb·2005-12-03
CVE-2005-4001 PHPYellowTM 5.33 - 'search_result.php?haystack' SQL Injection
PHPYellowTM 5.33 - 'search_result.php?haystack' SQL Injection
---
source: https://www.securityfocus.com/bid/15700/info
phpYellowTM is prone to multiple 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.
Successful exploitation could result in a compromise of the application, disclosure or modification of data, or may permit an attacker to exploit vulnerabilities in the underlying database implementation.
http://www.example.com/search_result.php?search=url&haystack=[SQL]
Exploit-DB
PHPYellowTM 5.33 - 'print_me.php?ckey' SQL Injection
exploitdb·2005-12-03
CVE-2005-4001 PHPYellowTM 5.33 - 'print_me.php?ckey' SQL Injection
PHPYellowTM 5.33 - 'print_me.php?ckey' SQL Injection
---
source: https://www.securityfocus.com/bid/15700/info
phpYellowTM is prone to multiple 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.
Successful exploitation could result in a compromise of the application, disclosure or modification of data, or may permit an attacker to exploit vulnerabilities in the underlying database implementation.
http://www.example.com/print_me.php?ckey=[SQL]
No writeups or analysis indexed.
http://pridels0.blogspot.com/2005/12/phpyellowtm-pro-edition-sql-inj-vuln.htmlhttp://secunia.com/advisories/17849http://www.osvdb.org/21428http://www.osvdb.org/21429http://www.securityfocus.com/bid/15700http://www.vupen.com/english/advisories/2005/2722http://pridels0.blogspot.com/2005/12/phpyellowtm-pro-edition-sql-inj-vuln.htmlhttp://secunia.com/advisories/17849http://www.osvdb.org/21428http://www.osvdb.org/21429http://www.securityfocus.com/bid/15700http://www.vupen.com/english/advisories/2005/2722
2005-12-05
Published