DotnetnukeApplication · Dnnsoftware

CVE-2025-32374

HIGH · 7.5 CVSS v3.1 Published 2025-04-09
Fix available
A fix is available. Upgrade to 9.13.8 or later.
See remediation →
84/100
Remediation priority · High
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. Possible denial of service with specially crafted information in the public registration form. This vulnerability is fixed in 9.13.8.

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 · moderate confidence

A denial of service vulnerability exists in DNN's public registration form where specially crafted input can cause the application to become unavailable. The vulnerability is triggered through the registration mechanism and affects all DNN installations below version 9.13.8.

MitigationUpgrade DNN to version 9.13.8 or later to remediate this vulnerability. Before upgrading, review customizations and test in a staging environment.

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:< 9.13.8

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Determine installed DNN version
    Access the DNN site as host/admin, navigate to Host > About or use the Persona Bar menu to view the version information. Alternatively, check the VERSION.txt file in the website root directory if accessible.
    Affected if The installed version is below 9.13.8 (any version from original installation up to 9.13.7)
  2. Verify public registration is enabled
    Log in as host or admin, go to Admin > Site Settings or Member Manager settings. Look for user registration settings - check if "Public" or "Verified" registration is allowed. This is typically found under Security Settings or Registration Settings.
    Affected if User registration is set to Public or Verified (allowing self-registration by anonymous users)
  3. Confirm registration form is publicly accessible
    Open a browser in incognito/private mode and attempt to access the registration page (typically at /Registration or /Register or ?ctl=Register). Verify the form loads without requiring authentication.
    Affected if The registration form loads and accepts input without requiring login credentials

Your environment is affected if DNN version is below 9.13.8 AND the public registration feature is enabled and accessible to anonymous users.

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 9.13.8 or later
Fixed in 9.13.8
Interim mitigation

Upgrade DNN to version 9.13.8 or later to remediate this vulnerability. Before upgrading, review customizations and test in a staging environment.

Recommended fix High confidence

DNN 9.13.8

  1. Backup your existing DNN installation and database before proceeding with any upgrade
  2. Download DNN version 9.13.8 from the official DNN repository or download page
  3. Review the official DNN upgrade instructions for your current version
  4. Execute the upgrade following the standard DNN upgrade procedure (typically involves uploading the installation package and running the upgrade wizard)
  5. Verify the upgrade was successful by checking the DNN admin dashboard
  6. Test the public registration form to ensure functionality is intact
Caveat No specific breaking changes documented in the provided CVE description

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

Fix this in Dotnetnuke Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,320
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-32374 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