# CVE-2025-64095: DNN Insufficient Access Control - Image Upload allows for Site Content Overwrite

> Unauthenticated attackers can upload and overwrite site files, enabling website defacement and potential XSS injection.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Oct 2025
- **Updated:** 29 Oct 2025
- **Also known as:** GHSA-3m8r-w7xg-jqvw

## What is CVE-2025-64095?

CVE-2025-64095 is a critical vulnerability in Dnnsoftware Dotnetnuke, published on 28 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

DNN (formerly DotNetNuke) is an open-source web content management platform (CMS) in the Microsoft ecosystem. Prior to 10.1.1, the default HTML editor provider allows unauthenticated file uploads and images can overwrite existing files. An unauthenticated user can upload and replace existing files allowing defacing a website and combined with other issue, injection XSS payloads. This vulnerability is fixed in 10.1.1.

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

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

2 open source packages ship an affected version, including DNN.PLATFORM. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `DNN.PLATFORM` | NuGet | All versions | 10.1.1 |
| `DNN.PLATFORM` | NuGet | All versions | 10.1.1 |

Products: Dnnsoftware Dotnetnuke.

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

Upgrade DNN.PLATFORM to 10.1.1 or later.

## Is CVE-2025-64095 being exploited?

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

Public exploit code:

- POC of DNN Insufficient Access Control - Image Upload allows for Site Content Overwrite (github_poc): https://github.com/h4x0r-dz/CVE-2025-64095---DNN-Unauthenticated-arbitrary-file-upload
- https://github.com/0xr2r/CVE-2025-64095 (github_poc): https://github.com/0xr2r/CVE-2025-64095
- DNN - Unrestricted Arbitrary File Upload (nuclei): http/cves/2025/CVE-2025-64095.yaml

## Other vulnerabilities in Dnnsoftware Dotnetnuke

- [CVE-2017-9822](https://insights.sbomify.com/CVE-2017-9822/): DotNetNuke (DNN) Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2018-15811](https://insights.sbomify.com/CVE-2018-15811/): DotNetNuke (DNN) Inadequate Encryption Strength (high 7.5, exploited in the wild)
- [CVE-2018-18325](https://insights.sbomify.com/CVE-2018-18325/): DotNetNuke (DNN) Inadequate Encryption Strength (high 7.5, exploited in the wild)
- [CVE-2006-3601](https://insights.sbomify.com/CVE-2006-3601/): Privilege escalation in n/a (critical 10.0)
- [CVE-2015-2794](https://insights.sbomify.com/CVE-2015-2794/): The installation wizard in DotNetNuke (DNN) allows privilege escalation (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-64095 is a critical vulnerability in Dnnsoftware Dotnetnuke, published on 28 Oct 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-64095 exists.

Affected packages and fixed versions:
- DNN.PLATFORM (NuGet): affected all versions; fixed in 10.1.1
- DNN.PLATFORM (NuGet): affected all versions; fixed in 10.1.1

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-64095/ (Markdown: https://insights.sbomify.com/CVE-2025-64095/index.md)
```

## Sources

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

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