# CVE-2026-17019: JetEngine < 3.8.13.1 - Unauthenticated Stored XSS via Form File Upload (SVG)

> Unauthenticated attackers can upload malicious SVG files to execute JavaScript in victims' browsers via stored XSS in the JetEngine plugin.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A: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:** 10 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-g5mm-h736-h3g3

## What is CVE-2026-17019?

CVE-2026-17019 is a medium-severity cross-site scripting vulnerability in Unknown JetEngine, published on 10 Aug 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

The JetEngine WordPress plugin before 3.8.13.1 does not sanitise uploaded SVG files before storing and serving them, and does not adequately restrict who can upload them, allowing unauthenticated attackers to upload a file containing malicious JavaScript that executes in the browser of any user who opens it (Stored Cross-Site Scripting).

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

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


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

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

## Is CVE-2026-17019 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-17019 is a medium-severity cross-site scripting vulnerability in Unknown JetEngine, published on 10 Aug 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-17019 exists.

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

## Sources

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

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