MySQL Eventum up to 1.5.5 class.auth.php insert email sql injection

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.9$0-$5k0.00

Summaryinfo

A vulnerability was found in MySQL Eventum up to 1.5.5. It has been rated as critical. Affected by this issue is the function insert of the file class.auth.php. This manipulation of the argument email causes sql injection. This vulnerability appears as CVE-2005-2468. The attack may be initiated remotely. In addition, an exploit is available.

Detailsinfo

A vulnerability was found in MySQL Eventum up to 1.5.5 (Database Software). It has been declared as critical. Affected by this vulnerability is the function insert of the file class.auth.php. The manipulation of the argument email with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. As an impact it is known to affect confidentiality, and integrity. The summary by CVE is:

Multiple SQL injection vulnerabilities in MySQL Eventum 1.5.5 and earlier allow remote attackers to execute arbitrary SQL commands via the (1) isCorrectPassword or (2) userExist function in class.auth.php, getCustomFieldReport function in (4) custom_fields.php, (5) custom_fields_graph.php, or (6) class.report.php, or the insert function in (7) releases.php or (8) class.release.php.

The weakness was presented 07/31/2005 by James Bercegay with Gulftech (Website). The advisory is shared at gulftech.org. This vulnerability is known as CVE-2005-2468 since 08/05/2005. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known. MITRE ATT&CK project uses the attack technique T1505 for this issue.

After even before and not, there has been an exploit disclosed. It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:class.auth.php it is possible to find vulnerable targets with Google Hacking. The commercial vulnerability scanner Qualys is able to test this issue with plugin 12172 (MySQL Eventum Multiple SQL Injection Vulnerabilities).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the databases at X-Force (21640), Exploit-DB (1134), SecurityFocus (BID 14437†), OSVDB (18403†) and Secunia (SA16304†). See VDB-1674, VDB-1673, VDB-1676 and VDB-1675 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.5
VulDB Meta Temp Score: 5.9

VulDB Base Score: 6.5
VulDB Temp Score: 5.9
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Sql injection
CWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Google Hack: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Qualys ID: 🔍
Qualys Name: 🔍

Exploit-DB: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

07/31/2005 🔍
07/31/2005 +0 days 🔍
08/01/2005 +0 days 🔍
08/01/2005 +0 days 🔍
08/01/2005 +0 days 🔍
08/01/2005 +0 days 🔍
08/05/2005 +3 days 🔍
08/05/2005 +0 days 🔍
12/31/2005 +148 days 🔍
01/03/2007 +368 days 🔍
03/12/2015 +2990 days 🔍
08/25/2025 +3819 days 🔍

Sourcesinfo

Advisory: gulftech.org
Researcher: James Bercegay
Organization: Gulftech
Status: Not defined
Confirmation: 🔍

CVE: CVE-2005-2468 (🔍)
GCVE (CVE): GCVE-0-2005-2468
GCVE (VulDB): GCVE-100-27853
X-Force: 21640
SecurityFocus: 14437 - MySQL Eventum Multiple SQL Injection Vulnerabilities
Secunia: 16304 - MySQL Eventum Cross-Site Scripting and SQL Injection, Moderately Critical
OSVDB: 18403 - MySQL Eventum login.php email Parameter SQL Injection Authentication Bypass
SecurityTracker: 1014603
Vulnerability Center: 13802 - MySQL Eventum 1.5.5 and Earlier Multiple SQL Injection Vulnerabilities, Medium
Vupen: ADV-2005-1287

scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍

Entryinfo

Created: 03/12/2015 11:11
Updated: 08/25/2025 04:59
Changes: 03/12/2015 11:11 (75), 07/13/2019 09:35 (7), 08/25/2025 04:59 (20)
Complete: 🔍
Cache ID: 216:B82:103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!