Skip to content
Fencer Vulns
high 8.8

CVE-2019-12095 json

Horde Trean, as used in Horde Groupware Webmail Edition through 5.2.22 and other products, allows CSRF, as demonstrated by the treanBookmar…

published 2019-10-24 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-3747

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.1%
EPSS 1.1% chance of exploitation in 30 days, percentile 66%
public exploits
0
none known

Summary

Horde Trean, as used in Horde Groupware Webmail Edition through 5.2.22 and other products, allows CSRF, as demonstrated by the treanBookmarkTags parameter to the trean/ URI on a webmail server. NOTE: treanBookmarkTags could, for example, be a stored XSS payload.

Patch / fix

  • php-horde Debian 12 5.2.21+debian0-1

debian advisories DEBIAN-CVE-2019-12095

Exploit prediction

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

Exploits and checks

  • numanozdemir.com https://numanozdemir.com/respdisc/horde/horde.mp4 referenced PoC, tagged "exploit" by a source, unverified
  • numanozdemir.com https://numanozdemir.com/respdisc/horde/horde.txt referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com https://packetstormsecurity.com/files/152975/Horde-Webmail-5.2.22-XSS-CSRF-SQL-Injection-Code-Execution.html referenced PoC, tagged "exploit" by a source, unverified
  • exploit-db.com https://www.exploit-db.com/exploits/46903 referenced PoC, tagged "exploit" by a source, unverified
  • cxsecurity.com https://cxsecurity.com/issue/WLB-2019050199 referenced PoC, tagged "exploit" by a source, unverified
  • bugs.horde.org https://bugs.horde.org/ticket/14926 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation
  • CWE-352 Cross-Site Request Forgery

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.