# CVE-2026-91922: Steedos Platform through 3.0.15-beta.47 Reflected XSS via page render

> Attackers can execute arbitrary JavaScript via crafted links to steal authentication tokens from victims using the Steedos Platform.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/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:** 15 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-925g-q5h8-6rmx

## What is CVE-2026-91922?

CVE-2026-91922 is a medium-severity cross-site scripting vulnerability in steedos-platform, published on 15 Sep 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

Steedos Platform through 3.0.15-beta.47 contains a reflected cross-site scripting vulnerability in the anonymous /api/page/render endpoint that fails to properly escape query parameters in inline script elements. Attackers can craft malicious links with script-terminating sequences in the schemaApi or data parameters to execute arbitrary JavaScript in victim sessions and steal X-Auth-Token credentials.

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

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


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

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

## Is CVE-2026-91922 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-91922 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-91922 is a medium-severity cross-site scripting vulnerability in steedos-platform, published on 15 Sep 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-91922 exists.

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

## Sources

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

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