Threats / Roundcube / CVE-2025-68461
CVE-2025-68461
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-19
Roundcube Webmail vulnerability
Roundcube Webmail contains a cross-site scripting vulnerability in SVG animate tag handling that allows injection of malicious scripts.
Verdict
Today item — known-exploited.
An attacker can inject malicious JavaScript through crafted SVG documents with animate tags in Roundcube Webmail. The vulnerability is actively exploited in the wild, enabling session hijacking, credential theft, and unauthorized mailbox access.
CISA KEV Yes · 2026-02-205EPSS 0.26842 (verify live)6CVSS 7.23CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
1 independent public report of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-02-20).
Probability (EPSS)
EPSS 0.26842 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 7.2 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N) · Affected: Roundcube, Webmail. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-79 Cross-site Scripting (XSS) — weakness family: Web / client.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 64 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft an SVG document with a malicious animate tag containing JavaScript payload.
Business
Webmail users receive emails or access content containing the malicious SVG without visible indicators of compromise.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I send the SVG-containing email to target users or host it where Roundcube will render it.
Business
The attack vector integrates seamlessly into normal email workflows, increasing likelihood of user interaction.
3
Lateral reach — past segmentation narrative 3
Attacker
I execute arbitrary JavaScript in the victim's browser within the Roundcube application context.
Business
Attacker gains access to session tokens, authentication cookies, and mailbox contents without additional authentication.
4
Data at risk — exfiltration narrative 4
Attacker
I exfiltrate sensitive emails, contacts, and credentials or perform actions on behalf of the user.
Business
Email accounts are compromised, enabling lateral movement, data theft, and further organizational compromise.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by mitreCNA
Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.