Debian LinuxOperating system · Debian
CVE-2018-19206
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 · uneditedsteps/mail/func.inc in Roundcube before 1.3.8 has XSS via crafted use of <svg><style>, as demonstrated by an onload attribute in a BODY element, within an HTML attachment.
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 confidenceRoundcube webmail before 1.3.8 contains a stored XSS vulnerability in steps/mail/func.inc. Attackers can craft malicious HTML email attachments using <svg><style> tags with an onload attribute in a BODY element to execute arbitrary JavaScript in the context of the victim's session when viewing the attachment.
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
= 9.0< 1.3.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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Roundcube versionCheck the Roundcube version by reviewing the changelog file (CHANGELOG or docs/CHANGELOG), the version.php file, or the HTML title on the login page. Common paths include /var/www/html/roundcube/ or /usr/share/roundcube/Affected if The installed version is lower than 1.3.8 (e.g., 1.3.7, 1.3.6, 1.2.x, etc.)
-
Confirm Debian package versionIf using Debian packages, run: dpkg -l | grep roundcube or apt-cache policy roundcubeAffected if The installed Debian roundcube package version is less than 1.3.8-1~deb9u1 (for Debian 9)
-
Check if HTML attachment rendering is enabledInspect Roundcube configuration file (config/main.inc.php or config/config.inc.php) for settings like: $config['show_html'] = true; or $config['inline_images'] = true; or $config['msg_seen'] options related to HTML displayAffected if HTML rendering for messages/attachments is enabled ($config['show_html'] = true or similar)
-
Verify vulnerable file existsCheck if the file steps/mail/func.inc exists in the Roundcube installation directory. This file contains the vulnerable code that does not properly sanitize HTML attachment contentAffected if The file steps/mail/func.inc exists and originates from a version before 1.3.8
You are affected if Roundcube version is below 1.3.8 AND HTML rendering for attachments/messages is enabled, allowing malicious <svg><style> HTML in email attachments to execute JavaScript in your session.
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.
From vendor data1.3.8
Upgrade Roundcube to version 1.3.8 or later to obtain the security fix. Alternatively, disable HTML rendering in mail attachments or sanitize attachment content before display.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-19206 — 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-2018-19206 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