Skip to main content
Mallory
MediumCISA KEVExploited in the wildPublic exploit

Stored XSS in Roundcube Webmail SVG email handling

IdentifiersCVE-2023-5631CWE-79· Improper Neutralization of Input…

CVE-2023-5631 is a stored cross-site scripting vulnerability in Roundcube Webmail caused by improper sanitization of malicious SVG content in HTML email messages. The issue is attributed to behavior in program/lib/Roundcube/rcube_washtml.php. A remote attacker can send a specially crafted HTML email containing an SVG document with attacker-controlled script payloads, including JavaScript embedded via constructs such as an onerror handler. When the victim views the message in Roundcube, the payload executes in the context of the victim’s authenticated Roundcube web session. The vulnerability affects Roundcube before 1.4.15, 1.5.x before 1.5.5, and 1.6.x before 1.6.4. Reporting indicates exploitation required no interaction beyond opening the malicious email in a browser-based Roundcube session.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows execution of arbitrary JavaScript in the security context of the victim’s Roundcube session. In observed attacks, this enabled loading of second-stage JavaScript from attacker infrastructure, enumeration of folders and messages in the current mailbox, and exfiltration of email contents to attacker-controlled servers. Because the code runs in the user’s authenticated webmail context, the attacker can effectively act as the victim within Roundcube, enabling mailbox compromise, intelligence collection, and follow-on phishing or account abuse.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by restricting access to Roundcube where feasible, closely monitoring for suspicious inbound HTML emails containing SVG content, and filtering or sanitizing SVG attachments and embedded SVG in email bodies at the mail gateway. Administrators should review web server and application logs for anomalous requests associated with message viewing and external JavaScript loads, and inspect for signs of mailbox enumeration or exfiltration. Because exploitation occurs in authenticated user sessions, user awareness alone is insufficient; compensating controls should focus on content filtering, network egress monitoring from webmail clients, and rapid patch deployment.

Remediation

Patch, then assume compromise.

Upgrade Roundcube to a fixed release: 1.4.15, 1.5.5, 1.6.4, or later, depending on the deployed branch. The vulnerable HTML sanitization behavior in rcube_washtml.php was patched by the Roundcube team on 2023-10-14, with security releases published on 2023-10-16. Organizations should prioritize patching internet-exposed Roundcube instances and verify that all webmail nodes in clustered or hosted environments are updated consistently.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
DebianDebian Linuxoperating_system
Fedora ProjectFedoraoperating_system
RoundcubeWebmailapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence4

Every observed campaign linking this CVE to a named adversary.

Associated malware4

Malware families riding this exploit, with evidence and IOCs.

Detection signatures1

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity1

Community discussion across Reddit, Mastodon, and other social sources.