# CVE-2026-5790: Stored Cross-Site Scripting (XSS) vulnerability in Stel Order

> Attackers can inject persistent scripts via legalName and employeeID parameters to steal session cookies and hijack user accounts.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 May 2026
- **Updated:** 14 May 2026
- **Also known as:** GHSA-vjqx-vf5x-gc8m

## What is CVE-2026-5790?

CVE-2026-5790 is a medium-severity cross-site scripting vulnerability in Stel Order, published on 14 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Stored Cross-Site Scripting (XSS) in Stel Order v3.25.1 and earlier, located at the ‘/app/FrontController’ endpoint via the ‘legalName’ and ‘employeeID’ parameters. The lack of proper input sanitization allows an attacker to inject malicious code that is persistently stored in the database. When other users or administrators access the affected sections, the code executes in their browsers, enabling the theft of session cookies and account hijacking.

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

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


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

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

## Is CVE-2026-5790 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-5790 is a medium-severity cross-site scripting vulnerability in Stel Order, published on 14 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-5790 in the wild and no public exploit code.

Affected product: Stel Order. 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-5790/ (Markdown: https://insights.sbomify.com/CVE-2026-5790/index.md)
```

## Sources

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

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