dbcve.org
DotnetnukeApplication · Dnnsoftware

CVE-2025-64095

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-28
Fix available
A fix is available. Upgrade to 10.1.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

DNN CMS versions prior to 10.1.1 contain a critical vulnerability in the default HTML editor provider that allows unauthenticated users to upload arbitrary files that can overwrite existing files on the server, enabling website defacement and potential XSS injection when combined with other vulnerabilities.

MitigationUpgrade to DNN version 10.1.1 or later, or apply the vendor-supplied security patch to remediate this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DotnetnukeApplication
Affected:< 10.1.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify DNN version
    Access the ~/admin/Settings/About.aspx page logged in as host, or check the web.config file for the Version element, or query the Database for the Version in the Portal table
    Affected if The installed version is any release prior to 10.1.1 (e.g., 10.0.0 through 10.1.0)
  2. Verify HTML editor provider
    Navigate to Host > Settings > Site Behavior > Default HTML Editor Provider. Confirm which provider is selected as the default
    Affected if The default HTML editor provider (typically 'TelerikEditorProvider' or 'DNNDefaultHtmlEditorProvider') is enabled and configured
  3. Check anonymous file upload access
    Attempt to access the file upload endpoint of the HTML editor without authentication. Common paths include /Providers/HtmlEditorProviders/Telerik/Upload.aspx or similar paths under /Providers/HtmlEditorProviders/
    Affected if The upload functionality is reachable without authentication or valid session
  4. Audit recently modified files
    Inspect the /Portals/[portalID]/ folders, especially subdirectories like /html/, /uploads/, or the specific editor's upload directory for files with recent modification timestamps or suspicious extensions (.asp, .aspx, .exe, .js)
    Affected if Unexpected files exist in these directories, particularly files with executable extensions or multiple .html files that were not intentionally created

You are affected if your DNN installation is version 10.1.0 or earlier AND the default HTML editor provider is enabled and accessible, allowing unauthenticated file uploads.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.1.1 or later
Fixed in 10.1.1
Interim mitigation

Upgrade to DNN version 10.1.1 or later, or apply the vendor-supplied security patch to remediate this vulnerability.

Recommended fix High confidence

DNN 10.1.1

  1. Create a complete backup of the DNN database and website files before proceeding with the upgrade
  2. Download DNN version 10.1.1 from the official DNN repository or distribution channel
  3. Follow the standard DNN upgrade procedure: stop the application pool, replace the core files with the new version files, restore any custom modules and skins, then restart the application pool
  4. Verify the upgrade was successful by logging into the DNN persona bar and checking the version number under Host > Host Settings
  5. Confirm the vulnerability is remediated by testing that the HTML editor file upload functionality now properly authenticates users and prevents overwriting existing files

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dotnetnuke Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64095 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-64095 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data