CVE-2023-5631
KEVRoundcube Webmail Persistent Cross-Site Scripting (XSS) Vulnerability
Description
Roundcube Webmail contains a persistent cross-site scripting (XSS) vulnerability that allows a remote attacker to run malicious JavaScript code.
Roundcube before 1.4.15, 1.5.x before 1.5.5, and 1.6.x before 1.6.4 allows stored XSS via an HTML e-mail message with a crafted SVG document because of program/lib/Roundcube/rcube_washtml.php behavior. This could allow a remote attacker to load arbitrary JavaScript code.
CVSS 3.1 vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NPublishedOct 18, 2023
Last modifiedJun 17, 2026
Added to KEVOct 26, 2023
Remediation dueNov 16, 2023
References
- openwall.com/lists/oss-security/2023/11/01/1Mailing ListThird Party Advisory
- openwall.com/lists/oss-security/2023/11/01/3Mailing ListThird Party Advisory
- openwall.com/lists/oss-security/2023/11/17/2Mailing ListThird Party Advisory
- bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054079Mailing ListPatch
- github.com/roundcube/roundcubemail/commit/41756cc3331b495cc0b71886984474dc529dd31dPatch
- github.com/roundcube/roundcubemail/commit/6ee6e7ae301e165e2b2cb703edf75552e5376613Patch
- github.com/roundcube/roundcubemail/issues/9168ExploitIssue Tracking
- github.com/roundcube/roundcubemail/releases/tag/1.4.15Release Notes
- github.com/roundcube/roundcubemail/releases/tag/1.5.5Release Notes
- github.com/roundcube/roundcubemail/releases/tag/1.6.4Release Notes
- lists.debian.org/debian-lts-announce/2023/10/msg00035.htmlMailing ListThird Party Advisory
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LK67Q46OIEGJCRQUBHKLH3IIJTBNGGX4/Mailing List
0 recent articles mention this CVE
68
Risk assessment · High
Actively exploited. Patch immediately.
- Exploitation
- Confirmed in the wild (CISA KEV)
- Federal remediation deadline
- Overdue by 1076 days
- CVSS
- 6.1 MEDIUM
- EPSS (30-day exploit probability)
- 76.3% · top 1% of all CVEs
- Weakness
- CWE-79
- Attack vector
- Network, remotely reachable
Recommended actions
- 1.Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
- 2.Treat as emergency change: patch or isolate internet-facing instances first.
- 3.Review exposure: confirm which instances are reachable from the internet and restrict access until patched.
- 4.Hunt for compromise: review logs for the disclosure window, not just from the patch date.
Assessment is derived automatically from the live signals above; verify against your own asset inventory.