Skip to content
Fencer Vulns
medium 6.4

CVE-2005-2468 json

Multiple SQL injection vulnerabilities in MySQL Eventum 1.5.5 and earlier allow remote attackers to execute arbitrary SQL commands via the…

published 2005-12-31 20 y ago modified 2026-06-16 4 mo ago also EUVD-2005-2469

cvss
6.4
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.0%
EPSS 2.0% chance of exploitation in 30 days, percentile 81%
public exploits
1
Exploit-DB

Summary

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.

Patch / fix

Timeline

  1. First public exploit (EDB-1134)
  2. Published

Exploit prediction

2.04% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • EDB-1134 MySQL Eventum 1.5.5 - 'login.php' SQL Injection webapps, 2005-08-05
  • osvdb.org http://www.osvdb.org/18404 referenced PoC, tagged "exploit" by a source, unverified
  • osvdb.org http://www.osvdb.org/18403 referenced PoC, tagged "exploit" by a source, unverified
  • osvdb.org http://www.osvdb.org/18405 referenced PoC, tagged "exploit" by a source, unverified
  • securitytracker.com http://securitytracker.com/id?1014603 referenced PoC, tagged "exploit" by a source, unverified
  • osvdb.org http://www.osvdb.org/18406 referenced PoC, tagged "exploit" by a source, unverified
  • gulftech.org http://www.gulftech.org/?node=research&article_id=00093-07312005 referenced PoC, tagged "exploit" by a source, unverified
  • securityfocus.com http://www.securityfocus.com/bid/14437 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 6.4 AV:N/AC:L/Au:N/C:P/I:P/A:N

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.