# CVE-2026-1010: Stored Cross-Site Scripting in Altium Enterprise Server Workflow Engine Allows Privilege Escalation

> Stored XSS in Altium Workflow Engine allows authenticated users to escalate privileges by injecting scripts executed in admin browsers.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Jan 2026
- **Updated:** 5 Feb 2026
- **Also known as:** GHSA-7wc5-cm44-jmh9

## What is CVE-2026-1010?

CVE-2026-1010 is a high-severity cross-site scripting vulnerability in Altium Enterprise Server, published on 15 Jan 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A stored cross-site scripting (XSS) vulnerability exists in the Altium Workflow Engine due to missing server-side input sanitization in workflow form submission APIs. A regular authenticated user can inject arbitrary JavaScript into workflow data.

When an administrator views the affected workflow, the injected payload executes in the administrator’s browser context, allowing privilege escalation, including creation of new administrator accounts, session token theft, and execution of administrative actions.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: Altium On-Prem Enterprise Server.

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

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

## Is CVE-2026-1010 being exploited?

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

Public exploit code:

- https://github.com/George0Papasotiriou/CVE-2026-1010-WebSocket-Connection-Smuggling-via-Malformed-Upgrade-Header (github_poc): https://github.com/George0Papasotiriou/CVE-2026-1010-WebSocket-Connection-Smuggling-via-Malformed-Upgrade-Header

## Other vulnerabilities in Altium Enterprise Server

- [CVE-2026-11414](https://insights.sbomify.com/CVE-2026-11414/): Hardcoded credentials in Altium Enterprise Server (critical 10.0)
- [CVE-2026-11420](https://insights.sbomify.com/CVE-2026-11420/): Path Traversal in Altium Enterprise Server NIS Allows Unauthenticated Arbitrary File Write and File Read (critical 10.0)
- [CVE-2026-11419](https://insights.sbomify.com/CVE-2026-11419/): Path Traversal in Altium Enterprise Server Vault UploadController Allows Arbitrary File Write (critical 9.4)
- [CVE-2025-27378](https://insights.sbomify.com/CVE-2025-27378/): SQL Injection in AES Due to Inactive SQL Parsing Configuration (high 8.6)
- [CVE-2025-27380](https://insights.sbomify.com/CVE-2025-27380/): HTML Injection Leading to Script Execution in Altium Enterprise Server (high 7.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-1010 is a high-severity cross-site scripting vulnerability in Altium Enterprise Server, published on 15 Jan 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-1010 in the wild and no public exploit code.

Affected product: Altium Enterprise Server. 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-1010/ (Markdown: https://insights.sbomify.com/CVE-2026-1010/index.md)
```

## Sources

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

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