CVE-2019-7213
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 6985 allows directory traversal. An authenticated user could delete arbitrary files or could create files in new folders in arbitrary locations on the mail server. This could lead to command execution on the server for instance by putting files inside the web directories.
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 confidenceSmarterTools SmarterMail 16.x before build 6985 contains a directory traversal vulnerability allowing authenticated users to delete arbitrary files or create files in arbitrary locations on the server. By placing files in web-accessible directories, an attacker could achieve command execution.
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.6985CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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.
-
Confirm SmarterMail is installedLook for SmarterMail installation directories (typically C:\Program Files\SmarterTools\SmarterMail or /opt/smartermail) or check for the SmarterMail service running on common ports (25, 587 for mail, 443 or 8080 for web interface)Affected if SmarterMail is not installed on the system
-
Identify the installed build versionAccess the SmarterMail web admin interface and navigate to Help > About, or check the service executable version properties, or look for a build number file in the installation directoryAffected if The build version cannot be determined or is not visible
-
Compare version against vulnerable rangeCheck if the installed build falls within >= 16.0.6345 and < 16.3.6985. For example, builds 16.0.6500 or 16.3.6000 would be vulnerable, while 16.0.6000 (below range) or 16.3.6985 (at or above fix) would not.Affected if The installed build number is 16.0.6345 or higher but lower than 16.3.6985
-
Verify web interface accessibilityConfirm the SmarterMail web interface (port 443/8443 or HTTP port 80/8080) is accessible from network or localhost. The vulnerability requires an authenticated user session.Affected if The web interface is exposed and user authentication is possible
-
Check user authentication is enabledVerify that user login functionality is enabled in SmarterMail. The directory traversal requires an authenticated user account to exploit.Affected if Authenticated user accounts can be created or exist in the system
You are affected if SmarterMail is installed with a build version between 16.0.6345 and 16.3.6984 inclusive, and the web interface with user authentication is accessible.
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.6985
Upgrade SmarterMail to build 6985 or later. As a secondary control, restrict authenticated user permissions to prevent access to sensitive filesystem locations.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7213 — 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-7213 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