# CVE-2025-32035: DNN does not check the contents of a file when uploading files

> Attackers can upload malicious executables disguised as images due to missing content validation, potentially leading to code execution if combined with other flaws.

- **Severity:** Low 2.6 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Apr 2025
- **Updated:** 8 Apr 2025
- **Also known as:** GHSA-8q89-mqw7-9pp7

## What is CVE-2025-32035?

CVE-2025-32035 is a low-severity vulnerability in Dnnsoftware Dotnetnuke, published on 8 Apr 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

DNN (formerly DotNetNuke) is an open-source web content management platform (CMS) in the Microsoft ecosystem. Prior to 9.13.2, when uploading files (e.g. when uploading assets), the file extension is checked to see if it's an allowed file type but the actual contents of the file aren't checked. This means that it's possible to e.g. upload an executable file renamed to be a .jpg. This file could then be executed by another security vulnerability. This vulnerability is fixed in 9.13.2.

Weakness: CWE-351 (Insufficient Type Distinction)

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

It affects 1 product.


Products: Dnnsoftware Dotnetnuke.

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

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

## Is CVE-2025-32035 being exploited?

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

## 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-2025-64095](https://insights.sbomify.com/CVE-2025-64095/): DNN Insufficient Access Control - Image Upload allows for Site Content Overwrite (critical 10.0)
- [CVE-2006-3601](https://insights.sbomify.com/CVE-2006-3601/): Privilege escalation in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-32035 is a low-severity vulnerability in Dnnsoftware Dotnetnuke, published on 8 Apr 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-32035 in the wild and no public exploit code.

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

## Sources

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

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