dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 13 Mar 2026.
WebmailApplication · Roundcube

CVE-2025-68461

MEDIUM · 6.1 CVSS v3.1 Published 2025-12-18
Fix available
A fix is available. Upgrade to 1.5.12 / 1.6.12 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Remotely reachable No privileges Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Roundcube Webmail before 1.5.12 and 1.6 before 1.6.12 is prone to a Cross-Site-Scripting (XSS) vulnerability via the animate tag in an SVG document.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Roundcube Webmail before versions 1.5.12 and 1.6.12 contains a stored XSS vulnerability in its SVG document rendering. Attackers can embed malicious JavaScript in the animate tag of an SVG file; when users view or interact with the crafted SVG, the script executes in their browser session, potentially stealing session cookies or performing actions as the victim.

MitigationUpgrade Roundcube Webmail to version 1.5.12 or 1.6.12 or later. If immediate patching is not possible, consider restricting or sanitizing SVG file uploads until the upgrade can be performed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WebmailApplication
Affected:< 1.5.12>= 1.6.0, < 1.6.12

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Roundcube version
    Check the version file or program output. Common locations: /usr/share/roundcube/version or CHANGELOG file in the installation directory, or run: composer show roundcube/roundcube or check the version displayed in the webmail login footer
    Affected if Version is below 1.5.12, or >= 1.6.0 and below 1.6.12
  2. Identify Roundcube installation directory
    Locate the Roundcube web root directory (commonly /var/www/roundcube, /usr/share/roundcube, or the document root for the webmail virtual host). Check your web server configuration for the document root pointing to Roundcube.
    Affected if Unable to locate installation directory for further checks
  3. Check if SVG rendering is enabled
    Inspect the Roundcube configuration file (usually config/main.inc.php or config/defaults.inc.php) for settings related to displaying image attachments or SVG handling. Look for options like show_images, display_attached_images, or svg_sanitization.
    Affected if SVG display or image embedding is enabled and the Roundcube version is vulnerable

User is affected if running Roundcube Webmail version 1.5.x below 1.5.12 or 1.6.x below 1.6.12 with SVG attachment/image display enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.5.12 / 1.6.12 or later
Fixed in 1.5.121.6.12
Vendor patch github.com →
Interim mitigation

Upgrade Roundcube Webmail to version 1.5.12 or 1.6.12 or later. If immediate patching is not possible, consider restricting or sanitizing SVG file uploads until the upgrade can be performed.

Recommended fix High confidence

Upgrade to Roundcube Webmail 1.5.12 (if on 1.5.x) or 1.6.12 (if on 1.6.x)

  1. 1. Backup your current Roundcube Webmail installation and database
  2. 2. Identify your current version (check in the 'program/include/iniset.php' or 'composer.json' file)
  3. 3. If using version 1.5.x: download Roundcube Webmail 1.5.12 from the official repository (https://github.com/roundcube/roundcubemail/releases/tag/1.5.12)
  4. 4. If using version 1.6.x: download Roundcube Webmail 1.6.12 from the official repository (https://github.com/roundcube/roundcubemail/releases/tag/1.6.12)
  5. 5. Extract the new version and replace the existing files, or use your package manager to upgrade
  6. 6. Clear any cached files (in the 'temp/' and 'cache/' directories)
  7. 7. Verify the upgrade was successful by checking the version number in the webmail interface
  8. 8. Test that the SVG rendering works correctly and the XSS vulnerability is mitigated
Caveat Security patch release with minimal expected breaking changes; always test in a staging environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Webmail Exploited in the wild — priority engagement
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-68461 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-68461 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data