# CVE-2025-28168: File upload in Multiple File Upload

> Attackers can upload arbitrary files by bypassing client-side validation in the Multiple File Upload add-on for OutSystems.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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:** Not needed
- **Fix available:** No
- **Published:** 5 May 2025
- **Updated:** 26 Aug 2025
- **Also known as:** GHSA-x9rr-xwxc-jcjf

## What is CVE-2025-28168?

CVE-2025-28168 is a medium-severity vulnerability in Multiple File Upload, published on 5 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Multiple File Upload add-on component 3.1.0 for OutSystems is vulnerable to Unrestricted File Upload. This occurs because file extension and size validations are enforced solely on the client side. An attacker can intercept the upload request and modify a parameter to bypass extension restrictions and upload arbitrary files. NOTE: this is a third-party component that is not supplied or supported by OutSystems.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-602 (Client-Side Enforcement of Server-Side Security)

## Which versions are affected by CVE-2025-28168?

It affects 1 product.


Products: Multiple File Upload Project Multiple File Upload.

## How do I fix CVE-2025-28168?

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

## Is CVE-2025-28168 being exploited?

There is no known exploitation of CVE-2025-28168 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-28168 and fix it if it is affected.

What it is: CVE-2025-28168 is a medium-severity vulnerability in Multiple File Upload, published on 5 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-28168 in the wild and no public exploit code.

Affected product: Multiple File Upload. 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-2025-28168/ (Markdown: https://insights.sbomify.com/CVE-2025-28168/index.md)
```

## Sources

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

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