Cyber Resilience

CVE-2025-32035

Dnnsoftware Dotnetnuke ≤ 9.13.2

Published
08 April 2025
Modified
26 August 2025
Patch / advisory
View advisory
CVSS Score v3.1 2.6
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:L/A:N
EPSS Score 0.0017 7th percentile
Risk Priority 24 floored blend · peak EPSS

Summary

CVE-2025-32035 is a low-severity Insufficient Type Distinction (CWE-351) vulnerability in Dnnsoftware Dotnetnuke. Its CVSS base score is 2.6 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 7th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and AC-16 (Security and Privacy Attributes) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)
CWE-351

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2017-9822Same product: Dnnsoftware Dotnetnuke
CVE-2025-52487Same product: Dnnsoftware Dotnetnuke
CVE-2026-40305Same product: Dnnsoftware Dotnetnuke
CVE-2025-59535Same product: Dnnsoftware Dotnetnuke
CVE-2026-24836Same product: Dnnsoftware Dotnetnuke
CVE-2026-24784Same product: Dnnsoftware Dotnetnuke
CVE-2025-59548Same product: Dnnsoftware Dotnetnuke
CVE-2015-2794Same product: Dnnsoftware Dotnetnuke
CVE-2025-52485Same product: Dnnsoftware Dotnetnuke
CVE-2025-64095Same product: Dnnsoftware Dotnetnuke

Affected Assets

dnnsoftware
dotnetnuke
≤ 9.13.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.5.3

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

Input validation can reject or correctly classify data whose type is ambiguous or incorrect, stopping the weakness at entry points.

AC-16 Security and Privacy Attributes partial match

Associating security and privacy attributes with objects supplies the mechanism needed to distinguish element types and enforce handling rules.

AC-4 Information Flow Enforcement partial match

Information flow enforcement requires explicit rules that distinguish information types or categories before permitting transfer.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent type-distinction flaws during development while the control addresses the full lifecycle.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect type confusion vulnerabilities before deployment.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle practices can include type-safe design and validation to reduce type confusion.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate explicit type handling and validation rules.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles encourage strong typing and clear type boundaries in system design.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly address proper type distinction and validation to prevent type-related flaws.

References