CVE-2005-3024: SQL Injection
Multiple SQL injection vulnerabilities in vBulletin 3.0.7 and earlier allow remote attackers to execute arbitrary SQL commands via the (1) announcement parameter to announcement.php, the (2) thread[forumid] or (3) criteria parameters to thread.php, (4) userid parameter to user.php, the (5) calendarcustomfieldid, (6) calendarid, (7) moderatorid, (8) holidayid, (9) calendarmoderatorid, or (10) calendar[0] parameters to admincalendar.php, (11) the cronid parameter to cronlog.php, (12) user[usergroupid][0] parameter to email.php, (13) help[0] parameter to help.php, the (14) limitnumber or (15) limitstart parameter to user.php, the (16) usertitleid or (17) ids parameters to usertitle.php, (18) rvt[0] parameter to language.php, (19) keep[0] parameter to phrase.php, (20) dostyleid parameter to template.php, (21) thread[forumid] parameter to thread.php, or (22) usertools.php.
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2005-3024?
CVE-2005-3024 is classified as a medium severity vulnerability due to its potential to allow attackers to execute arbitrary SQL commands.
How do I fix CVE-2005-3024?
To fix CVE-2005-3024, users should upgrade to vBulletin version 3.0.8 or later, which contains patches addressing these SQL injection vulnerabilities.
What versions of vBulletin are affected by CVE-2005-3024?
CVE-2005-3024 affects vBulletin versions 3.0.7 and earlier, as well as various earlier versions in the 2.x series.
What are the potential impacts of exploiting CVE-2005-3024?
Exploiting CVE-2005-3024 may allow attackers to manipulate the database, access sensitive data, or perform actions on behalf of legitimate users.
How can I determine if my vBulletin installation is vulnerable to CVE-2005-3024?
To determine if your vBulletin installation is vulnerable to CVE-2005-3024, check the version number against the known affected versions and review any security logs for suspicious activity.