CVE-2019-7214

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-24. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
9.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 85%
CISA-KEV: Not listedEPSS: 85%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

SmarterTools SmarterMail 16.x before build 6985 allows deserialization of untrusted data. An unauthenticated attacker could run commands on the server when port 17001 was remotely accessible. This port is not accessible remotely by default after applying the Build 6985 patch.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
83(Track*)
EG Risk 83/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation85% × 40%
Automatability30% × 15%
Action: Watch closely — could escalate to Attend.
EPSS
99.7%
KEV
Not listed

Published

April 24, 2019

Last Modified

November 21, 2024

Advisory Details (3)

Auto-updated Jun 13, 2026
No patch confirmed yet.
generic

SmarterMail Additions, Changes and Fixes

https://www.smartertools.com/smartermail/release-notes/current
generic

Packet Storm

http://packetstormsecurity.com/files/173388/SmarterTools-SmarterMail-Remote-Code-Execution.html
generic

Packet Storm

http://packetstormsecurity.com/files/160416/SmarterMail-6985-Remote-Code-Execution.html

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 27× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 01:46 UTCEG score recompute
  2. 2026-07-22 22:29 UTCEG score recompute
  3. 2026-07-22 14:05 UTCEPSS rescore
  4. 2026-07-21 15:22 UTCEPSS rescore
  5. 2026-07-21 15:22 UTCEPSS rescore
  6. 2026-07-18 10:02 UTCEPSS rescore
  7. 2026-07-15 16:55 UTCEPSS rescore
  8. 2026-07-13 22:27 UTCEPSS rescore
  9. 2026-07-13 22:27 UTCEPSS rescore
  10. 2026-07-13 06:10 UTCEPSS rescore
  11. 2026-07-13 06:10 UTCEPSS rescore
  12. 2026-07-12 05:44 UTCEPSS rescore
  13. 2026-07-12 05:43 UTCEPSS rescore
  14. 2026-07-11 08:24 UTCEPSS rescore
  15. 2026-07-11 08:24 UTCEPSS rescore
  16. 2026-07-08 15:11 UTCEPSS rescore
  17. 2026-07-07 13:43 UTCEPSS rescore
  18. 2026-07-05 02:27 UTCEPSS rescore
  19. 2026-07-01 15:03 UTCEPSS rescore
  20. 2026-07-01 15:03 UTCEPSS rescore
  21. 2026-06-30 23:20 UTCEPSS rescore
  22. 2026-06-29 14:03 UTCEPSS rescore
  23. 2026-06-27 03:06 UTCEPSS rescore
  24. 2026-06-24 14:03 UTCEPSS rescore
  25. 2026-06-24 14:03 UTCEPSS rescore
Show 31 more
  1. 2026-06-23 21:31 UTCEPSS rescore
  2. 2026-06-23 21:31 UTCEPSS rescore
  3. 2026-06-22 14:23 UTCEPSS rescore
  4. 2026-06-22 14:23 UTCEPSS rescore
  5. 2026-06-21 14:54 UTCEPSS rescore
  6. 2026-06-21 14:54 UTCEPSS rescore
  7. 2026-06-21 01:57 UTCEPSS rescore
  8. 2026-06-21 01:57 UTCEPSS rescore
  9. 2026-06-16 17:50 UTCEPSS rescore
  10. 2026-06-15 17:46 UTCEPSS rescore
  11. 2026-06-14 23:15 UTCEPSS rescore
  12. 2026-06-14 23:15 UTCEPSS rescore
  13. 2026-06-12 23:09 UTCEPSS rescore
  14. 2026-06-12 23:09 UTCEPSS rescore
  15. 2026-06-10 22:16 UTCEPSS rescore
  16. 2026-06-10 22:16 UTCEPSS rescore
  17. 2026-06-10 13:19 UTCEPSS rescore
  18. 2026-06-06 13:45 UTCEPSS rescore
  19. 2026-06-06 13:45 UTCEPSS rescore
  20. 2026-06-05 22:45 UTCEPSS rescore
  21. 2026-06-05 06:08 UTCEPSS rescore
  22. 2026-06-01 13:50 UTCEPSS rescore
  23. 2026-06-01 13:50 UTCEPSS rescore
  24. 2026-05-29 13:42 UTCEPSS rescore
  25. 2026-05-28 13:43 UTCEPSS rescore
  26. 2026-05-28 13:43 UTCEPSS rescore
  27. 2026-05-27 20:11 UTCEG score recompute
  28. 2026-05-27 20:11 UTCGHSA enrichment
  29. 2026-05-27 13:39 UTCEPSS rescore
  30. 2026-05-27 13:38 UTCEPSS rescore
  31. 2026-05-25 23:46 UTCOSV refresh

Publicly available exploits

(4 references)

Working exploit code is in the public domain (1 Metasploit module) (2 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCDrew-Alleman/CVE-2019-7214
    First seen Mar 7, 2025

    Python3 Rewrite of SmarterMail < Build 6985 Remote Code Execution found by 1F98D (CVE-2019-7214) POC

    Open source ↗
  • GitHub PoCdevzspy/CVE-2019-7214
    First seen Dec 20, 2020

    Collection of PoCs created for SmarterMail < Build 6985 RCE

    Open source ↗
  • Exploit-DBEDB-49216
    First seen Dec 9, 2020

    SmarterMail Build 6985 - Remote Code Execution

    Open source ↗
  • Metasploitexploit/windows/http/smartermail_rce✓ verified
    First seen Apr 17, 2019

    SmarterTools SmarterMail less than build 6985 - .NET Deserialization Remote Code Execution

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2019-7214?
CVE-2019-7214 is a critical vulnerability published on April 24, 2019. SmarterTools SmarterMail 16.x before build 6985 allows deserialization of untrusted data. An unauthenticated attacker could run commands on the server when port 17001 was remotely accessible. This port is not accessible remotely by default after applying the Build 6985 patch.
When was CVE-2019-7214 disclosed?
CVE-2019-7214 was first published in the National Vulnerability Database on April 24, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-7214 actively exploited?
CVE-2019-7214 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-7214?
CVE-2019-7214 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2019-7214?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-7214, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2019-7214

Explore →

Is Your Infrastructure Affected by CVE-2019-7214?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs