Skip to content
Fencer Vulns
medium 5.8

CVE-2005-2467 json

Multiple cross-site scripting (XSS) vulnerabilities in MySQL Eventum 1.5.5 and earlier allow remote attackers to inject arbitrary web scrip…

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

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

Summary

Multiple cross-site scripting (XSS) vulnerabilities in MySQL Eventum 1.5.5 and earlier allow remote attackers to inject arbitrary web script or HTML via the (1) id parameter to view.php, (2) release parameter to list.php, or (3) F parameter to get_jsrs_data.php.

Patch / fix

Timeline

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

Exploit prediction

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

Exploits and checks

  • EDB-26058 MySQL AB Eventum 1.x - 'get_jsrs_data.php?F' Cross-Site Scripting webapps, 2005-08-01
  • EDB-26057 MySQL AB Eventum 1.x - 'list.php?release' Cross-Site Scripting webapps, 2005-08-01
  • EDB-26056 MySQL AB Eventum 1.x - 'view.php?id' Cross-Site Scripting webapps, 2005-08-01
  • securitytracker.com http://securitytracker.com/id?1014603 referenced PoC, tagged "exploit" by a source, unverified
  • securityfocus.com http://www.securityfocus.com/bid/14436 referenced PoC, tagged "exploit" by a source, unverified
  • osvdb.org http://www.osvdb.org/18401 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
  • osvdb.org http://www.osvdb.org/18400 referenced PoC, tagged "exploit" by a source, unverified
  • osvdb.org http://www.osvdb.org/18402 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 5.8 AV:N/AC:M/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.