CVE-2009-1810 json
Multiple SQL injection vulnerabilities in myColex 1.4.2 allow remote attackers to execute arbitrary SQL commands via (1) the formUser param…
published 2009-05-29 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-1805
- cvss
- 6.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 59%
- public exploits
- 1
- Exploit-DB
Summary
Multiple SQL injection vulnerabilities in myColex 1.4.2 allow remote attackers to execute arbitrary SQL commands via (1) the formUser parameter (aka the Name field) to common/login.php, and allow remote authenticated users to execute arbitrary SQL commands via the ID parameter in a Detail action to (2) kategorie.php, (3) medium.php, (4) person.php, or (5) schlagwort.php in modules/, related to classes/class.perform.php.
Patch / fix
- collector.ch/drupal5/?q=node/39 advisory
Timeline
- First public exploit (EDB-8707)
- Published
Exploit prediction
0.89% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-8707 my-colex 1.4.2 - Authentication Bypass / SQL Injection / Cross-Site Scripting webapps, 2009-05-15
- securityfocus.com http://www.securityfocus.com/bid/34997 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.0 | AV:N/AC:M/Au:S/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
collector.ch
/drupal5/?q=node/39
patch, vendor-advisory
-
exploit-db.com
/exploits/8707
exploit
-
securityfocus.com
/bid/34997
vdb-entry, exploit
-
secunia.com
/advisories/35111
third-party-advisory, vendor-advisory
-
vupen.com
/english/advisories/2009/1344
vdb-entry
Sources
- CVE List CVE-2009-1810
- NVD CVE-2009-1810
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.