dbcve.org
SmartermailApplication · Smartertools

CVE-2021-32234

CRITICAL · 9.8 CVSS v3.1 Published 2021-11-17
Fix available
A fix is available. Upgrade to 100.0.7803 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
SmarterTools SmarterMail 16.x through 100.x before 100.0.7803 allows remote code execution.

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

SmarterTools SmarterMail versions 16.x through 100.x prior to 100.0.7803 contains a critical remote code execution vulnerability (CVSS 9.8) that allows unauthenticated attackers to execute arbitrary code on the affected server.

MitigationUpgrade SmarterMail to version 100.0.7803 or later. Given the critical severity and RCE capability, prioritize patching immediately and review server access logs for indicators of compromise.

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
SmartermailApplication
Affected:>= 16.0.6345, < 100.0.7803

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Confirm Smartermail is installed
    Check for Smartermail installation directory or service on the system. Look for 'SmarterMail' in installed programs or running services.
    Affected if SmarterTools Smartermail software is present on the server
  2. Determine installed Smartermail version
    Locate the version information typically found in the Smartermail installation, often accessible through the web interface login page or in application logs. Compare the build number to the affected range.
    Affected if Installed version is 16.0.6345 or higher but lower than 100.0.7803
  3. Check network exposure
    Determine if the Smartermail web interface (typically ports 80, 443, or 8080/8443) is accessible from untrusted networks. Verify firewall rules and binding configurations.
    Affected if The Smartermail web interface is exposed to the internet or untrusted networks without proper network segmentation
  4. Review access logs for indicators
    Examine Smartermail logs for suspicious requests, especially those targeting authentication endpoints or unusual API calls from unknown IP addresses.
    Affected if Unusual unauthenticated requests appear in logs, particularly from unfamiliar IP addresses

The server is affected if Smartermail version is 16.0.6345 or higher but below 100.0.7803 and the service is network-accessible.

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 100.0.7803 or later
Fixed in 100.0.7803
Interim mitigation

Upgrade SmarterMail to version 100.0.7803 or later. Given the critical severity and RCE capability, prioritize patching immediately and review server access logs for indicators of compromise.

Recommended fix High confidence

100.0.7803 or later

  1. 1. Identify the current SmarterMail version by checking the help/about section in the Smartermail web interface or via PowerShell Get-Process on the server
  2. 2. Download SmarterMail version 100.0.7803 or later from the official SmarterTools download page (www.smartertools.com)
  3. 3. Before upgrading, perform a complete backup of the SmarterMail system including configuration files, mail stores, and database
  4. 4. Stop the SmarterMail service before applying the upgrade
  5. 5. Run the installer for the new version (100.0.7803 or later)
  6. 6. Follow the installation wizard prompts to complete the upgrade
  7. 7. Start the SmarterMail service after installation completes
  8. 8. Verify the upgrade was successful by checking the version in the about section

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

Fix this in Smartermail Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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