# CVE-2025-15109: jackq XCMS upload.php unrestricted upload

> Remote attackers can upload malicious files via an unrestricted upload vulnerability in the XCMS web application, potentially leading to code execution.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Dec 2025
- **Updated:** 24 Feb 2026
- **Also known as:** GHSA-f342-w736-j52r

## What is CVE-2025-15109?

CVE-2025-15109 is a medium-severity vulnerability in jackq XCMS, published on 27 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw has been found in jackq XCMS up to 3fab5342cc509945a7ce1b8ec39d19f701b89261. This impacts an unknown function of the file Public/javascripts/admin/plupload-2.1.2/examples/upload.php. This manipulation causes unrestricted upload. It is possible to initiate the attack remotely. The exploit has been published and may be used. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are available. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2025-15109 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-15109 is a medium-severity vulnerability in jackq XCMS, published on 27 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15109 exists.

Affected product: jackq XCMS. 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-15109/ (Markdown: https://insights.sbomify.com/CVE-2025-15109/index.md)
```

## Sources

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

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