# CVE-2026-120016: Cross-Site Scripting (XSS) vulnerability in SAP NetWeaver Visual Composer


- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-jw3m-69w7-hwhg

## What is CVE-2026-120016?

CVE-2026-120016 is a medium-severity vulnerability in SAP_SE SAP NetWeaver Visual Composer, published on 10 Nov 2026. 

### Official description

SAP NetWeaver Visual Composer does not perform sufficient input validation and output encoding on certain request data. An unauthenticated attacker could craft a malicious link containing specially crafted input. If a victim clicks the link, the injected script executes in the victim's browser within the context of the affected application. This results in a low impact on confidentiality and integrity. There is no impact on availability.

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

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


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

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

## Is CVE-2026-120016 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120016 is a medium-severity vulnerability in SAP_SE SAP NetWeaver Visual Composer, published on 10 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120016 in the wild and no public exploit code.

Affected product: SAP_SE SAP NetWeaver Visual Composer. 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-120016/ (Markdown: https://insights.sbomify.com/CVE-2026-120016/index.md)
```

## Sources

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

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