# CVE-2026-90931: LaraDashboard 0.9.0 through 1.2.2 Stored XSS via SVG Upload

> Authenticated users can upload malicious SVG files to execute scripts in admin sessions, leading to account takeover.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **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:** 14 Sep 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-9gxw-qpx8-x9c7, GHSA-qxqf-9qjp-qgw3

## What is CVE-2026-90931?

CVE-2026-90931 is a medium-severity cross-site scripting vulnerability in laradashboard, published on 14 Sep 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

LaraDashboard versions 0.9.0 through 1.2.2 fail to sanitize SVG file content during media upload, allowing authenticated users with only the media.create permission to upload malicious SVG files containing script tags. When any user including administrators opens the stored SVG file served inline from the application origin, the embedded JavaScript executes in the dashboard context, enabling session hijacking and administrative account takeover.

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

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


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

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

## Is CVE-2026-90931 being exploited?

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

Public exploit code:

- CVE-2026-90931: LaraDashboard stored XSS via SVG upload — bilingual analysis and safe PoC (github_poc): https://github.com/capivara-research/CVE-2026-90931

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90931 is a medium-severity cross-site scripting vulnerability in laradashboard, published on 14 Sep 2026. Any signed-in user can exploit it over the network, 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-90931 exists.

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

## Sources

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

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