# CVE-2025-69906: File upload in n/a

> Attackers can upload malicious files to Monstra CMS via the Files Manager plugin to achieve remote code execution.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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 Feb 2026
- **Updated:** 6 Feb 2026
- **Also known as:** GHSA-gcf9-q9xj-jjx5

## What is CVE-2025-69906?

CVE-2025-69906 is a high-severity vulnerability in n/a, published on 5 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Monstra CMS v3.0.4 contains an arbitrary file upload vulnerability in the Files Manager plugin. The application relies on blacklist-based file extension validation and stores uploaded files directly in a web-accessible directory. Under typical server configurations, this can allow an attacker to upload files that are interpreted as executable code, resulting in remote code execution.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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

It affects 1 product.


Products: Monstra Monstra Cms.

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

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

## Is CVE-2025-69906 being exploited?

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

Public exploit code:

- https://github.com/cypherdavy/CVE-2025-69906-Monstra-CMS-3.0.4-Arbitrary-File-Upload-to-RCE (github_poc): https://github.com/cypherdavy/CVE-2025-69906-Monstra-CMS-3.0.4-Arbitrary-File-Upload-to-RCE

## Other vulnerabilities in n/a

- [CVE-2018-11678](https://insights.sbomify.com/CVE-2018-11678/): Security feature bypass in n/a (critical 9.8)
- [CVE-2020-23219](https://insights.sbomify.com/CVE-2020-23219/): Code injection in n/a (high 8.8)
- [CVE-2020-13978](https://insights.sbomify.com/CVE-2020-13978/): Command injection in n/a (high 7.2)
- [CVE-2020-20691](https://insights.sbomify.com/CVE-2020-20691/): File upload in n/a (medium 6.5)
- [CVE-2018-11227](https://insights.sbomify.com/CVE-2018-11227/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-69906 is a high-severity vulnerability in n/a, published on 5 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-69906 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-2025-69906/ (Markdown: https://insights.sbomify.com/CVE-2025-69906/index.md)
```

## Sources

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

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