CVE-2005-4189 json
Multiple cross-site scripting (XSS) vulnerabilities in Horde Kronolith H3 before 2.0.6 allow remote authenticated users to inject arbitrary…
published 2005-12-13 20 y ago modified 2026-06-16 4 mo ago also EUVD-2005-4184
- cvss
- 3.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 73%
- public exploits
- 0
- none known
Summary
Multiple cross-site scripting (XSS) vulnerabilities in Horde Kronolith H3 before 2.0.6 allow remote authenticated users to inject arbitrary web script or HTML via (1) the Calendar name field when creating calendars, (2) event title field when deleting events, the (3) Category and (4) Location search fields, and the (5) attendees email address fields when editing event attendees, and possibly other vectors.
Patch / fix
- osvdb.org/21609 patch
- osvdb.org/21608 patch
- securityfocus.com/bid/15808 patch
- osvdb.org/21611 patch
- osvdb.org/21610 patch
- lists.horde.org/archives/announce/2005/000234.html patch
- secunia.com/advisories/17971 advisory
Exploit prediction
1.43% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 3.5 | AV:N/AC:M/Au:S/C:N/I:P/A:N |
References
-
osvdb.org
/21609
vdb-entry, patch
-
osvdb.org
/21608
vdb-entry, patch
-
secunia.com
/advisories/17971
third-party-advisory, patch, vendor-advisory
-
securityfocus.com
/bid/15808
vdb-entry, patch
-
osvdb.org
/21611
vdb-entry, patch
-
osvdb.org
/21610
vdb-entry, patch
-
lists.horde.org
/archives/announce/2005/000234.html
mailing-list, patch
-
debian.org
/security/2006/dsa-970
vendor-advisory
-
archives.neohapsis.com
/archives/fulldisclosure/2005-12/0459.html
mailing-list, vendor-advisory
-
sec-consult.com
/245.html
vendor-advisory
-
secunia.com
/advisories/18827
third-party-advisory
-
vupen.com
/english/advisories/2005/2834
vdb-entry
Sources
- CVE List CVE-2005-4189
- NVD CVE-2005-4189
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.