CVE-2019-7211
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 · uneditedSmarterTools SmarterMail 16.x before build 6995 has stored XSS. JavaScript code could be executed on the application by opening a malicious email or when viewing a malicious file 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 confidenceStored XSS vulnerability in SmarterTools SmarterMail 16.x before build 6995 allows remote attackers to inject malicious JavaScript via email messages or file attachments. When victims open the malicious email or view the malicious attachment, the embedded JavaScript executes in their browser context.
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>= 16.0.6345, < 16.3.6955CVSS 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.
-
Confirm SmarterMail installationCheck if SmarterMail is installed on the system by looking for the installation directory (typically C:\Program Files\SmarterTools\SmarterMail\) or by accessing the web admin interface on port 9998 or 17001.Affected if SmarterMail is installed and accessible
-
Locate the installed versionAccess the SmarterMail web interface, navigate to the About or System Info page (usually under Settings > System > About), or check the version information in the Windows Programs and Features list.Affected if The version cannot be determined or the application is not visible in expected locations
-
Identify the build numberOn the About page in SmarterMail admin interface, locate the full build number (e.g., 16.3.6955). The build number is displayed as a four or five digit number after the version major.minor.Affected if The build number is visible but falls within the range 6345 to 6954 (or specifically less than 6995)
-
Compare against affected version rangeCompare your installed build number to the affected range: versions 16.0.6345 and above through versions below 16.3.6995 are vulnerable. If your build shows 16.3.6954 or lower, you are in the affected range.Affected if Installed build is >= 6345 and < 6995 (or specifically < 16.3.6955)
You are affected if SmarterMail is installed and the detected build number is 16.0.6345 or higher but lower than build 6995 (or 16.3.6955).
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 data16.3.6955
Upgrade to SmarterMail build 6995 or later which contains the security patch. Implement input sanitization and output encoding for email content and attachments as a defense-in-depth measure.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7211 — 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-2019-7211 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