Skip to content
Fencer Intel
low 2.7

CVE-2019-13458 json

An issue was discovered in Open Ticket Request System (OTRS) 7.0.x through 7.0.8, and Community Edition 5.0.x through 5.0.36 and 6.0.x thro…

published 7y ago modified 4mo ago also EUVD-2019-4931

cvss
2.7
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.5%
EPSS 1.5% chance of exploitation in 30 days, percentile 75%
public exploits
0
none known

Summary

An issue was discovered in Open Ticket Request System (OTRS) 7.0.x through 7.0.8, and Community Edition 5.0.x through 5.0.36 and 6.0.x through 6.0.19. An attacker who is logged into OTRS as an agent user with appropriate permissions can leverage OTRS notification tags in templates in order to disclose hashed user passwords.

Patch / fix

  • otrs2 Debian 11 6.0.20-1

debian advisories DEBIAN-CVE-2019-13458

  • otrs2 Ubuntu 20.04 LTS 6.0.20-1

ubuntu advisories UBUNTU-CVE-2019-13458

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • otrs Package Hub 15 SP2 6.0.29-bp152.2.8.1
  • otrs Package Hub 15 SP2, Package Hub 15 SP1, openSUSE Leap 15.2 +1 more 6.0.29-bp152.2.5.4
  • otrs Package Hub 15 SP1, Package Hub 15, openSUSE Leap 15.1 5.0.42-bp151.3.3.1

opensuse advisories openSUSE-SU-2020:1509-1openSUSE-SU-2020:1475-1openSUSE-SU-2020:0551-1

Is CVE-2019-13458 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

Exploit prediction

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

CVSS scores

assigned by version score vector
CNA 3.0 2.7 CVSS:3.0/AC:L/AV:N/A:N/C:L/I:N/PR:H/S:U/UI:N
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CNA 3.0 2.7 CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:P/I:N/A:N

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.