# CVE-2019-7211: Cross-site scripting in n/a

> Attackers can execute arbitrary JavaScript in SmarterMail via malicious emails or attachments, potentially compromising user accounts.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2vcv-3hqm-h975

## What is CVE-2019-7211?

CVE-2019-7211 is a medium-severity cross-site scripting vulnerability in n/a, published on 24 Apr 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

SmarterTools SmarterMail 16.x before build 6995 has stored XSS. JavaScript code could be executed on the application by opening a malicious email or when viewing a malicious file attachment.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2019-7211?

It affects 1 product.


Products: Smartertools Smartermail.

## How do I fix CVE-2019-7211?

No fix has been published for CVE-2019-7211 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-7211 being exploited?

There is no known exploitation of CVE-2019-7211 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2025-52691](https://insights.sbomify.com/CVE-2025-52691/): SmarterTools SmarterMail Unrestricted Upload of File with Dangerous Type (critical 10.0, exploited in the wild)
- [CVE-2026-24423](https://insights.sbomify.com/CVE-2026-24423/): SmarterTools SmarterMail Missing Authentication for Critical Function (critical 9.3, exploited in the wild)
- [CVE-2026-23760](https://insights.sbomify.com/CVE-2026-23760/): SmarterTools SmarterMail Authentication Bypass Using an Alternate Path or Channel (critical 9.3, exploited in the wild)
- [CVE-2021-32234](https://insights.sbomify.com/CVE-2021-32234/): Code injection in n/a (critical 9.8)
- [CVE-2019-7214](https://insights.sbomify.com/CVE-2019-7214/): Deserialization in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-7211 and fix it if it is affected.

What it is: CVE-2019-7211 is a medium-severity cross-site scripting vulnerability in n/a, published on 24 Apr 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-7211 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-7211/ (Markdown: https://insights.sbomify.com/CVE-2019-7211/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-7211
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-7211
- OSV: https://osv.dev/vulnerability/CVE-2019-7211

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-7211/
Summaries are generated and may contain mistakes; the official description above is the record.