Skip to content
Fencer Intel
medium 5.3

CVE-2013-6365 json

Horde Groupware Web mail 5.1.2 has CSRF with requests to change permissions

published 7y ago modified 4mo ago also EUVD-2013-6190

cvss
5.3
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 64%
public exploits
0
none known

Summary

Horde Groupware Web mail 5.1.2 has CSRF with requests to change permissions

Patch / fix

  • php-horde Debian 12 5.1.5+debian0-1
  • php-horde-kronolith Debian 12 4.1.4-1

debian advisories DEBIAN-CVE-2013-6365

Is CVE-2013-6365 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2013-6365 updated cvss 4.3

horde: CSRF in changing permissions functionality

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.07% chance of exploitation in the next 30 days, higher than 64% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • bugzilla.redhat.com https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-6365 referenced PoC, tagged "exploit" by a source, unverified
  • securityfocus.com https://www.securityfocus.com/archive/1/529590 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Classification

Weakness
  • CWE-352 Cross-Site Request Forgery

References

Sources

Fencer Intel 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.