What is CVE-2025-68461?
CVE-2025-68461 is a Cross-Site Scripting (XSS) vulnerability in Roundcube Webmail’s handling of SVG content. The issue involves the SVG <animate> tag, where crafted SVG content can lead to script execution in a victim’s browser when the content is rendered by the webmail UI. Roundcube addressed this in its security updates released in December 2025, and upstream credits the report to Valentin T. (CrowdStrike). As of February 20, 2026, the CVE is also listed in CISA’s Known Exploited Vulnerabilities (KEV) catalog (as reflected in the NVD record), indicating evidence of exploitation.
What is Affected By CVE-2025-68461?
Roundcube Webmail deployments running vulnerable 1.5.x or 1.6.x builds are affected. According to public advisories and the NVD record, the vulnerable ranges include the 1.5 LTS branch prior to 1.5.12 and the 1.6 branch prior to 1.6.12. In practice, this matters most anywhere Roundcube renders HTML email and permits SVG content to pass through its sanitization pipeline.
Affected versions (upstream):
-
Roundcube 1.5.x: < 1.5.12
-
Roundcube 1.6.x: 1.6.0 – 1.6.11 (i.e., < 1.6.12)
-
Note on 1.7 prereleases: Roundcube also states the fix is included in 1.7 RC2 (and later prereleases), for environments tracking the 1.7 line before a final 1.7 stable.
Mitigation and Remediation For CVE-2025-68461
The primary remediation is to upgrade Roundcube to a fixed release that includes the SVG animate-tag sanitization fix. Roundcube strongly recommends upgrading production installations, and the upstream patch specifically targets sanitizer behavior around SVG animation attributes. If immediate patching is not possible, reduce exposure by limiting the chances that malicious SVG content is rendered in user sessions and by tightening web-facing controls around the webmail interface.
Recommended actions:
-
Upgrade Roundcube to 1.6.12+ (or 1.5.12+ for the 1.5 LTS line).
-
If you are testing 1.7 prereleases, ensure you are on 1.7 RC2 or later that includes the same security fixes.
-
Add compensating controls until patching is complete:
-
Filter or strip
image/svg+xml(SVG) content at your mail gateway/content filter if business requirements allow. -
Harden access to webmail (e.g., restrict by VPN/SSO, limit exposure to trusted networks, enforce MFA on accounts).
-
Review browser-side protections via your reverse proxy (security headers, isolation policies) to reduce blast radius if an XSS lands.
-
-
Treat this as time-sensitive: the NVD record reflects KEV inclusion (Date Added 2026-02-20) with a published remediation due date for U.S. agencies (a strong signal of operational risk).
Impact of Successful Exploitation of CVE-2025-68461
Successful exploitation can allow an attacker’s script to run in the context of a user’s Roundcube web session. That can translate into data exposure and unauthorized actions performed as the victim within the webmail interface, depending on session protections and deployment specifics. Because XSS executes inside the browser, the most realistic outcomes often involve reading displayed mailbox content, triggering state-changing actions, or capturing session-relevant tokens when protections are weak. The NVD record’s KEV indicator suggests defenders should assume credible real-world attacker interest and usage.
Potential impacts include:
-
Mailbox data exposure (reading messages/contacts visible to the session)
-
Unauthorized actions as the victim (sending email, changing settings, creating rules/filters where available)
-
Session compromise risks (depending on cookie flags, token handling, and browser protections)
-
Follow-on social engineering (webmail UI manipulation to trick users into revealing credentials or taking unsafe actions)
Proof of Concept for CVE-2025-68461
Public descriptions indicate the vulnerable condition is triggered by crafted SVG content using the <animate> tag. The following is a non-weaponized, educational test pattern you can use only in a controlled lab (e.g., a local test user sending mail to another local test user on a deliberately vulnerable Roundcube instance) to confirm whether your sanitizer blocks the technique after upgrading. Upstream’s fix is implemented in the Roundcube sanitizer code (see the referenced patch commit) and should prevent this style of SVG animate-tag abuse in patched versions.
<svg xmlns=“http://www.w3.org/2000/svg”>
<a>
<!– The risky behavior described publicly is animation-driven attribute manipulation.
Patched versions should neutralize/strip dangerous cases. –>
<animate attributeName=“xlink:href”
values=“javascript:alert(‘test’)”
begin=“0s” />
Click
</a>
</svg>
Defensive validation checklist:
-
Verify your Roundcube version is 1.5.12+ or 1.6.12+ (or 1.7 RC2+ if applicable).
-
Render the test message in the web UI and confirm the SVG is sanitized/neutralized (no script execution, and ideally the dangerous attribute handling is removed).
-
If you must assess exposure without testing payloads, rely on version-based validation and upgrade evidence (release notes/vendor advisory + deployed package version).