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 14 Nov 2024.
Debian LinuxOperating system · Debian

CVE-2024-37383

MEDIUM · 6.1 CVSS v3.1 Published 2024-06-07
Fix available
A fix is available. Upgrade to 1.5.7 / 1.6.7 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS 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.7 and 1.6.x before 1.6.7 allows XSS via SVG animate attributes.

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 versions before 1.5.7 and 1.6.7 are vulnerable to stored cross-site scripting (XSS) attacks via SVG animate attributes. An attacker can craft malicious SVG content in email messages that, when rendered, executes arbitrary JavaScript in the context of the victim's session.

MitigationUpgrade Roundcube Webmail to version 1.5.7, 1.6.7, or later. Until patched, consider restricting HTML rendering or sanitizing incoming email content from untrusted sources.

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
Debian LinuxOperating system
Affected:= 10.0
WebmailApplication
Affected:< 1.5.7>= 1.6.0, < 1.6.7

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. Identify the installed Roundcube Webmail version
    Check the version file in the Roundcube installation directory, typically located at program/include/rcube_version.php, or look for a version indicator in the main program files
    Affected if The installed version is before 1.5.7, or is 1.6.0 through 1.6.6 (meaning < 1.6.7)
  2. Confirm file upload functionality is enabled
    Review the Roundcube configuration file (usually config/main.inc.php or config/config.inc.php) for the $config['enable_file_upload'] setting
    Affected if File uploads are enabled ($config['enable_file_upload'] is set to true) - this is required for the attack vector to work
  3. Check MIME type filtering for attachments
    Examine the Roundcube configuration for $config['mime_types'] or $config['allowed_mime_types'] settings to see if SVG files are accepted as uploads
    Affected if SVG MIME types (image/svg+xml) are not explicitly blocked in the allowed MIME types configuration, meaning users can upload SVG files
  4. Inspect uploaded attachment directories for SVG files
    Locate the attachments directory (commonly at temp/ or plugins/attachments/ in the Roundcube data directory) and list any .svg files present
    Affected if SVG files exist in the attachments storage - these could contain malicious animated script elements if uploaded by an attacker

You are affected if the installed Roundcube version is vulnerable (< 1.5.7 or >= 1.6.0 but < 1.6.7) AND file uploads are enabled, allowing users to upload SVG files that could contain XSS payloads.

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.7 / 1.6.7 or later
Fixed in 1.5.71.6.7
Vendor patch github.com →
Interim mitigation

Upgrade Roundcube Webmail to version 1.5.7, 1.6.7, or later. Until patched, consider restricting HTML rendering or sanitizing incoming email content from untrusted sources.

Recommended fix High confidence

Upgrade to Roundcube Webmail 1.5.7 or 1.6.7 (latest stable 1.6.x recommended)

  1. 1. Backup your Roundcube Webmail installation and database before proceeding
  2. 2. Determine your current version by checking the version file (typically in program/include/iniset.php or similar)
  3. 3. If you are on a version < 1.5.7, upgrade to 1.5.7; if you are on version >= 1.6.0 but < 1.6.7, upgrade to 1.6.7
  4. 4. Download the appropriate fixed release from the official Roundcube repository (github.com/roundcube/roundcubemail)
  5. 5. Extract the new version and replace the existing files, preserving your configuration (typically in config/ directory)
  6. 6. Run any pending database schema updates if the installer prompts (or use the bin/updatedb.sh script)
  7. 7. Clear application caches (delete contents of temp/ and cache/ directories)
  8. 8. Verify the upgrade by logging in and checking the about/version information
Caveat Review release notes for breaking changes between your current version and target version before upgrading

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

Fix this in Debian Linux Exploited in the wild — priority engagement
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,100
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-37383 — 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-2024-37383 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