# CVE-2026-119680: Stored Cross-Site Scripting (XSS) in SharePoint Manager Plus Chart Feature


- **Severity:** High 8.5 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:L/VA:N/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 30 Oct 2026
- **Updated:** 6 Nov 2026
- **Also known as:** GHSA-4rm7-wmp2-9p6w

## What is CVE-2026-119680?

CVE-2026-119680 is a high-severity vulnerability in ManageEngine SharePoint Manager Plus, published on 30 Oct 2026. 

### Official description

A stored cross-site scripting (XSS) vulnerability exists in the chart feature of SharePoint Manager Plus (SPMP) due to improper sanitization and HTML encoding of user-controlled data. An attacker can inject malicious HTML or JavaScript into attributes used to generate charts, including users' full names, site names, or group names. The injected content is stored and subsequently executed in the context of other users' browsers when the affected charts are rendered. This vulnerability was fixed in client application build 4508.

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

## Which versions are affected by CVE-2026-119680?


## How do I fix CVE-2026-119680?

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

## Is CVE-2026-119680 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119680 and fix it if it is affected.

What it is: CVE-2026-119680 is a high-severity vulnerability in ManageEngine SharePoint Manager Plus, published on 30 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-119680 in the wild and no public exploit code.

Affected product: ManageEngine SharePoint Manager Plus. 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-2026-119680/ (Markdown: https://insights.sbomify.com/CVE-2026-119680/index.md)
```

## Sources

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

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