# CVE-2019-16949: Business logic in n/a

> Attackers can modify chat log email recipients and content via POST requests, enabling phishing campaigns against users on the same domain.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Nov 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3xcg-m3v5-m392

## What is CVE-2019-16949?

CVE-2019-16949 is a medium-severity vulnerability in n/a, published on 13 Nov 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in Enghouse Web Chat 6.1.300.31 and 6.2.284.34. A user is allowed to send an archive of their chat log to an email address specified at the beginning of the chat (where the user enters in their name and e-mail address). This POST request can be modified to change the message as well as the end recipient of the message. The e-mail address will have the same domain name and user as the product allotted. This can be used in phishing campaigns against users on the same domain.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Enghouse Web Chat.

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

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

## Is CVE-2019-16949 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-16948](https://insights.sbomify.com/CVE-2019-16948/): Server-side request forgery in n/a (critical 9.8)
- [CVE-2020-13972](https://insights.sbomify.com/CVE-2020-13972/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2019-16950](https://insights.sbomify.com/CVE-2019-16950/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2019-16951](https://insights.sbomify.com/CVE-2019-16951/): Server-side request forgery in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-16949 is a medium-severity vulnerability in n/a, published on 13 Nov 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-16949 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-16949/ (Markdown: https://insights.sbomify.com/CVE-2019-16949/index.md)
```

## Sources

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

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