# CVE-2017-16962: Cross-site scripting in n/a

> Stored XSS in CommuniGate Pro WebMail allows attackers to execute scripts via crafted calendar invites or emails, potentially leading to account takeover.

- **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:** 27 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3cqh-3p38-9v4j

## What is CVE-2017-16962?

CVE-2017-16962 is a medium-severity cross-site scripting vulnerability in n/a, published on 27 Nov 2017. 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

The WebMail components (Crystal, pronto, and pronto4) in CommuniGate Pro before 6.2.1 have stored XSS vulnerabilities via (1) the location or details field of a Google Calendar invitation, (2) a crafted Outlook.com calendar (aka Hotmail Calendar) invitation, (3) e-mail granting access to a directory that has JavaScript in its name, (4) JavaScript in a note name, (5) JavaScript in a task name, or (6) HTML e-mail that is mishandled in the Inbox component.

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

## Which versions are affected by CVE-2017-16962?

It affects 1 product.


Products: Communigate Communigate Pro.

## How do I fix CVE-2017-16962?

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

## Is CVE-2017-16962 being exploited?

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

Public exploit code:

- CommuniGatePro 6.1.16 - Cross-Site Scripting (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2018-18621](https://insights.sbomify.com/CVE-2018-18621/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-16962 and fix it if it is affected.

What it is: CVE-2017-16962 is a medium-severity cross-site scripting vulnerability in n/a, published on 27 Nov 2017. 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-2017-16962 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-2017-16962/ (Markdown: https://insights.sbomify.com/CVE-2017-16962/index.md)
```

## Sources

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

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