Skip to content
Fencer Intel
high 7.4

CVE-2019-15237 json

Roundcube Webmail through 1.3.9 mishandles Punycode xn-- domain names, leading to homograph attacks.

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

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

Summary

Roundcube Webmail through 1.3.9 mishandles Punycode xn-- domain names, leading to homograph attacks.

Patch / fix

  • roundcube Debian 14, Debian 13, Debian 12 1.5.0+dfsg.1-1

debian advisories DEBIAN-CVE-2019-15237

  • roundcube Ubuntu 22.04 LTS 1.5.0+dfsg.1-2
  • roundcube Ubuntu Pro 16.04 LTS 1.2~beta+dfsg.1-0ubuntu1+esm8
  • roundcube Ubuntu Pro 18.04 LTS 1.3.6+dfsg.1-1ubuntu0.1~esm8
  • roundcube Ubuntu Pro 20.04 LTS 1.4.3+dfsg.1-1ubuntu0.1~esm8

ubuntu advisories UBUNTU-CVE-2019-15237

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

Is CVE-2019-15237 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-2019-15237 updated cvss 6.5

roundcube: mishandling of Punycode xn-- domain name leads to homograph attack

  • 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.03% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 7.4 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/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.