# CVE-2026-4950: Stored Cross-Site Scripting in CustomerAdministration Portal (KundenManager) in VertiGIS WebOrderSystem


- **Severity:** Medium 4.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-g5vv-w6m9-qrh6

## What is CVE-2026-4950?

CVE-2026-4950 is a medium-severity vulnerability in VertiGIS Ltd. WebOrderSystem (KundenManager), published on 23 Oct 2026. 

### Official description

The CustomerAdministration portal (KundenManager) of VertiGIS WebOrderSystem allows privileged users to manage the employees of defined companies (user groups). User properties, for example the "secondName" parameter, can be filled with JavaScript code while editing a user. The code is stored and executed in the browser of any other privileged user who opens the edited user entry or the user overview of the corresponding user group. An authenticated attacker with access to the portal can use this to run script code in the session of other portal users. Version 7.0.8.6, the latest available at the time of testing, is affected. The vendor did not provide information about further affected versions.

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

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


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

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

## Is CVE-2026-4950 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-4950 is a medium-severity vulnerability in VertiGIS Ltd. WebOrderSystem (KundenManager), published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-4950 in the wild and no public exploit code.

Affected product: VertiGIS Ltd. WebOrderSystem (KundenManager). 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-4950/ (Markdown: https://insights.sbomify.com/CVE-2026-4950/index.md)
```

## Sources

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

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