# CVE-2025-8265: 299Ko CMS File Management view unrestricted upload

> Attackers can upload malicious files to the 299Ko CMS file manager, potentially leading to remote code execution.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jul 2025
- **Updated:** 28 Jul 2025
- **Also known as:** GHSA-mj82-h8g3-6cr5

## What is CVE-2025-8265?

CVE-2025-8265 is a medium-severity vulnerability in 299Ko CMS, published on 28 Jul 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability classified as critical has been found in 299Ko CMS 2.0.0. This affects an unknown part of the file /admin/filemanager/view of the component File Management. The manipulation leads to unrestricted upload. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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

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


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

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

## Is CVE-2025-8265 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-8265 is a medium-severity vulnerability in 299Ko CMS, published on 28 Jul 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-8265 exists.

Affected product: 299Ko CMS. 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-8265/ (Markdown: https://insights.sbomify.com/CVE-2025-8265/index.md)
```

## Sources

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

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