CVE-2006-0167
published 2006-01-11CVE-2006-0167: SQL injection vulnerability in MyPhPim 01.05 allows remote attackers to execute arbitrary SQL commands via the (1) cal_id parameter in calendar.php3 and the…
PriorityP344high7.5CVSS 2.0
AVNACLAuNCPIPAP
EXPLOIT
EPSS
2.19%
80.2th percentile
SQL injection vulnerability in MyPhPim 01.05 allows remote attackers to execute arbitrary SQL commands via the (1) cal_id parameter in calendar.php3 and the (2) password field on the login page.
Affected
1 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| myphpim | myphpim | — | — |
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
MyPHPim - 'calendar.php3?cal_id' SQL Injection
exploitdb·2006-01-11
CVE-2006-0167 MyPHPim - 'calendar.php3?cal_id' SQL Injection
MyPHPim - 'calendar.php3?cal_id' SQL Injection
---
source: https://www.securityfocus.com/bid/16210/info
MyPhPim is prone to multiple input validation vulnerabilities. These issues are due to a failure in the application to properly sanitize user-supplied input.
Successful exploitation of these vulnerabilities could result in a compromise of the application, disclosure or modification of data, the theft of cookie-based authentication credentials. They may also permit an attacker to exploit vulnerabilities in the underlying database implementation as well as other attacks.
http://www.example.com/myphpim/calendar.php3?menu=detail&cal_id=999%20union%20select%201,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17/*
Exploit-DB
MyPHPim - Login Page pass Field SQL Injection
exploitdb·2006-01-11
CVE-2006-0167 MyPHPim - Login Page pass Field SQL Injection
MyPHPim - Login Page pass Field SQL Injection
---
source: https://www.securityfocus.com/bid/16210/info
MyPhPim is prone to multiple input validation vulnerabilities. These issues are due to a failure in the application to properly sanitize user-supplied input.
Successful exploitation of these vulnerabilities could result in a compromise of the application, disclosure or modification of data, the theft of cookie-based authentication credentials. They may also permit an attacker to exploit vulnerabilities in the underlying database implementation as well as other attacks.
login: [first registered user]
pass: a") or "a"="a"/*
No writeups or analysis indexed.
http://evuln.com/vulns/22/summary.htmlhttp://secunia.com/advisories/18399http://www.osvdb.org/22324http://www.osvdb.org/22325http://www.securityfocus.com/archive/1/421863/100/0/threadedhttp://www.securityfocus.com/bid/16210http://www.vupen.com/english/advisories/2006/0147https://exchange.xforce.ibmcloud.com/vulnerabilities/24066https://exchange.xforce.ibmcloud.com/vulnerabilities/24075http://evuln.com/vulns/22/summary.htmlhttp://secunia.com/advisories/18399http://www.osvdb.org/22324http://www.osvdb.org/22325http://www.securityfocus.com/archive/1/421863/100/0/threadedhttp://www.securityfocus.com/bid/16210http://www.vupen.com/english/advisories/2006/0147https://exchange.xforce.ibmcloud.com/vulnerabilities/24066https://exchange.xforce.ibmcloud.com/vulnerabilities/24075
2006-01-11
Published