SmarterTools SmarterMail 16.x before build 6985 has hardcoded secret keys.

published 2019-04-24 7y ago modified 2026-06-17 4mo ago also EUVD-2019-16756

cvss: 8.2; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.0%; EPSS 1.0% chance of exploitation in 30 days, percentile 63%
public exploits: 0; none known

SmarterTools SmarterMail 16.x before build 6985 has hardcoded secret keys. An unauthenticated attacker could access other users’ emails and file attachments. It was also possible to interact with mailing lists.

Patch / fix

fixed in 1

smartertools smartermail 16.3.6985

Is CVE-2019-7212 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.01% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

smartertools.com https://www.smartertools.com/smartermail/release-notes/current referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.0	8.2	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
NVD	2.0	6.4	AV:N/AC:L/Au:N/C:P/I:P/A:N

Classification

Weakness

CWE-798 Use of Hard-coded Credentials

References

smartertools.com /smartermail/release-notes/current
exploit, release-notes, vendor-advisory
nccgroup.trust /uk/our-research/technical-advisory-multiple-vulnerabilities-in-smartermail/
third-party-advisory

Sources

CVE List CVE-2019-7212
NVD CVE-2019-7212

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.