CVE-2024-42008
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 · uneditedA Cross-Site Scripting vulnerability in rcmail_action_mail_get->run() in Roundcube through 1.5.7 and 1.6.x through 1.6.7 allows a remote attacker to steal and send emails of a victim via a malicious e-mail attachment served with a dangerous Content-Type header.
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 confidenceCross-Site Scripting (XSS) vulnerability in Roundcube's rcmail_action_mail_get->run() function allows remote attackers to execute malicious scripts via email attachments with crafted Content-Type headers, potentially enabling theft and unauthorized sending of victim emails.
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< 1.5.8>= 1.6.0, < 1.6.8CVSS 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
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Roundcube installation and locate version fileLocate the Roundcube installation directory and find the VERSION file (typically in the root installation folder or program/include/rcmail.php) to read the installed version numberAffected if The installed version is < 1.5.8 OR (>= 1.6.0 AND < 1.6.8)
-
Confirm Roundcube version against affected rangesCompare your installed version number to the affected ranges: versions < 1.5.8 OR versions >= 1.6.0 but < 1.6.8 are vulnerableAffected if Version falls within < 1.5.8 or >= 1.6.0 and < 1.6.8
-
Check if automatic attachment rendering is enabledInspect the Roundcube configuration files (config/defaults.inc.php or config/config.inc.php) for the 'inline_attachments' or 'show_images' setting that controls automatic rendering of email attachmentsAffected if Automatic attachment rendering or inline image display is enabled in the configuration
-
Verify if the vulnerable code path is accessibleConfirm that the rcmail_action_mail_get action is accessible in your Roundcube installation by checking that the mail plugin and attachment viewing features are activeAffected if The mail plugin with attachment viewing capability is enabled and accessible to users
You are affected if your Roundcube installation version is less than 1.5.8 or between 1.6.0 and 1.6.8, AND automatic attachment rendering is enabled in your configuration.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.5.81.6.8
Upgrade to Roundcube 1.5.8 or 1.6.8 or later; until then, disable automatic attachment rendering and implement strict Content-Type validation for email attachments.
Roundcube Webmail 1.5.8 or 1.6.8
- 1. Identify current Roundcube version by checking the version file or changelog
- 2. Back up the entire Roundcube installation and database before upgrading
- 3. For the 1.5.x branch: upgrade to version 1.5.8
- 4. For the 1.6.x branch: upgrade to version 1.6.8
- 5. Apply the upgrade using your package manager or by downloading the new version from roundcube.net
- 6. Clear any cached files (temp/, cache/ directories)
- 7. Verify the upgrade was successful and test that email attachments render correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,568.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-42008 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-42008 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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