dbcve.org
DotnetnukeApplication · Dnnsoftware

CVE-2025-52488

HIGH · 8.6 CVSS v3.1 Published 2025-06-21
Fix available
A fix is available. Upgrade to 10.0.1 or later.
See remediation →
95/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. In versions 6.0.0 to before 10.0.1, DNN.PLATFORM allows a specially crafted series of malicious interaction to potentially expose NTLM hashes to a third party SMB server. This issue has been patched in version 10.0.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 (DotNetNuke) CMS versions 6.0.0 through 10.0.0 contain a vulnerability allowing attackers to potentially expose NTLM authentication hashes to a third-party SMB server through a specially crafted series of malicious interactions, likely involving server-side request forgery or similar injection mechanism.

MitigationUpgrade DNN to version 10.0.1 or later. If immediate upgrading is not possible, consider disabling NTLM authentication, implementing SMB signing, and blocking outbound SMB connections to untrusted servers at the network perimeter.

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:>= 6.0.0, < 10.0.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
Changed
Confidentiality
High
Integrity
None
Availability
None

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

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. Locate the DNN installation
    Search for the file '~/web.config' or '~/Documentation/Version.txt' in the web root. DNN typically stores its version in the web.config assembly version or in a Version.txt file in the root folder.
    Affected if DNN CMS is present on the server
  2. Determine the installed DNN version
    Open the web.config file and locate the 'version' attribute in the 'assembly' element under 'system.web/compilation', or check the Version.txt file if present. Note the full version number (e.g., 9.11.0, 10.0.0).
    Affected if The version cannot be determined or the file is missing
  3. Compare version against affected range
    Verify the installed version falls within >= 6.0.0 and < 10.0.1. If the version is 10.0.1 or later, the vulnerability is not present. Document the exact version found.
    Affected if Installed version is 6.0.0 through 10.0.0 inclusive
  4. Identify if outbound SMB connectivity is possible
    Review network firewall rules or web server outbound restrictions. Check if the DNN server can initiate outbound SMB (TCP port 445) connections to arbitrary hosts.
    Affected if Outbound SMB connections are allowed and the DNN version is within the affected range

The environment is affected if DNN CMS is installed with a version between 6.0.0 and 10.0.0 and the server can make outbound SMB connections.

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.0.1 or later
Fixed in 10.0.1
Interim mitigation

Upgrade DNN to version 10.0.1 or later. If immediate upgrading is not possible, consider disabling NTLM authentication, implementing SMB signing, and blocking outbound SMB connections to untrusted servers at the network perimeter.

Recommended fix High confidence

10.0.1

  1. Backup the existing DNN database and all site files
  2. Download DNN Platform version 10.0.1 from the official DNN repository or website
  3. Review the DNN upgrade documentation for version-specific migration notes
  4. Place the site in maintenance mode or take it offline
  5. Extract and deploy the 10.0.1 files to the production server, preserving the web.config and any custom configurations
  6. Run the upgrade installation by accessing the site - DNN will automatically execute database migrations
  7. Verify the upgrade was successful by logging into the DNN Persona Bar
  8. Test critical functionality including user authentication and content management
Caveat Major version upgrades from 6.x/7.x/8.x/9.x to 10.x may include breaking changes in APIs, modules, and extensions - test thoroughly in a staging environment before production deployment

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-52488 — 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-52488 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