Search | Research | Contact Us Friday March 2, 2022
Most Viewed Items
  1 PHPXMLRPC Library Remote Code Execution
  2 Multiple Invision Power Board Vulnerabilities
  3 XOOPS 2.0.11 && Earlier Multiple Vulnerabilities
  4 Mambo Multiple Vulnerabilities
  5 PEAR XML_RPC Library Remote Code Execution
  6 eBay And Amazon Still Vulnerable
  7 Woltlab Burning Board SQL Injection Vulnerability
  8 When Small Mistakes Can Cause Big Problems
  9 WordPress And Earlier Multiple Vulnerabilities
10 MySQL Eventum Multiple Vulnerabilities
Need Secure Code?
Quick Search
You can use the form below to search our site. Just enter the keywords to search.
Home Services Archives Research Downloads Contact
MySQL Eventum Multiple Vulnerabilities
July 31, 2021
Vendor : MySQL AB
Version : MySQL Eventum <= 1.5.5
Risk : Multiple Vulnerabilities

Eventum is a user-friendly and flexible issue tracking system that can be used by a support department to track incoming technical support requests, or by a software development team to quickly organize tasks and bugs. Eventum is used by the MySQL AB Technical Support team. Unfortunately Eventum is vulnerable to some highly exploitable SQL Injection issues as well as cross site scripting issues. A new version of Eventum has been released and users are strongly advised to upgrade their Eventum installations.

Cross Site Scripting:
There are a number of cross site scripting issues in MySQL Eventum. You can find several examples of these issues below.


A malicious user can exploit these vulnerabilities to steal sensitive user based information, or render hostile script in the context of the victim's web browser.

SQL Injection:
MySQL Eventum is a very well written program, and does a good job to protect against harmful input. However, there are a few some what blind SQL Injection issues in Eventum, and these issues are very exploitable. First, let's have a look at /includes/class.auth.php
     * Checks whether the provided password match against the email 
     * address provided.
     * @access  public
     * @param   string $email The email address to check for
     * @param   string $password The password of the user to check for
     * @return  boolean
    function isCorrectPassword($email, $password)
        $stmt = "SELECT usr_password FROM " . APP_DEFAULT_DB . "." . APP_TABLE_PREFIX . "
	user WHERE usr_email='$email'";
        $passwd = $GLOBALS["db_api"]->dbh->getOne($stmt);
        if (PEAR::isError($passwd)) {
            Error_Handler::logError(array($passwd->getMessage(), $passwd->getDebugInfo()), 
	    __FILE__, __LINE__);
            return false;
        } else {
            if ($passwd != md5($password)) {
                return false;
            } else {
                return true;

MySQL Eventum usually sanitizes within functions, so as expected the $email variable is never sanitized before being passed to this vulnerable function. Also, if the target host is using a database that supports UNION functionality then we can overwrite the expected returned password, and bypass the password check! The above issue is very dangerous, but there is a nearly identical function used alongside the isCorrectPassword function named userExists() and it is vulnerable in an almost identical manner. In addition to the "pre-auth" SQL Injection vulns are a few other SQL Injection vulnerabilities.


The above is a rough outline of the other vulnerable functions that have been patched in the recent 1.6.0 release. Users should upgrade immediately.

A new version of MySQL Eventum has been released. The official release notes can be found at the link below.

Special thanks to Joao Prado Maia from the MySQL Eventum team for a very quick resolution of these issues.

James Bercegay of the GulfTech Security Research Team