# CVE-2026-75308: Cross-site scripting in n/a

> Attackers can upload malicious HTML or executable files via the upload endpoint, leading to cross-site scripting and potential code execution.

- **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:** 9 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-wvvf-rj6j-5fcw

## What is CVE-2026-75308?

CVE-2026-75308 is a medium-severity cross-site scripting vulnerability in n/a, published on 9 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

yshopmall <=3.3 is vulnerable to Cross Site Scripting (XSS). The file upload endpoint /api/upload of the system lacks file type validation. Attackers can upload files of any type, including HTML, JSP, and other executable files.

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

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


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

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

## Is CVE-2026-75308 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-75308 is a medium-severity cross-site scripting vulnerability in n/a, published on 9 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-75308 exists.

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

## Sources

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

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