# CVE-2026-33653: Uploady Vulnerable to Stored Cross-Site Scripting (XSS)

> Attackers can inject malicious scripts via filenames that execute in victims' browsers when viewing file lists, requiring an upgrade to fix.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A: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:** 26 Mar 2026
- **Updated:** 27 Mar 2026
- **Also known as:** GHSA-2834-m7xm-fqr5

## What is CVE-2026-33653?

CVE-2026-33653 is a medium-severity cross-site scripting vulnerability in farisc0de Uploady, published on 26 Mar 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

Ulloady is a file uploader script with multi-file upload support. A Stored Cross-Site Scripting (XSS) vulnerability exists in versions prior to 3.1.2 due to improper sanitization of filenames during the file upload process. An attacker can upload a file with a malicious filename containing JavaScript code, which is later rendered in the application without proper escaping. When the filename is displayed in the file list or file details page, the malicious script executes in the browser of any user who views the page. Version 3.1.2 fixes the issue.

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

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

It affects 1 product.


Products: Farisc0de Uploady.

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

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

## Is CVE-2026-33653 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-33653 is a medium-severity cross-site scripting vulnerability in farisc0de Uploady, published on 26 Mar 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-33653 exists.

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

## Sources

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

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