dbcve.org
DotnetnukeApplication · Dnnsoftware

CVE-2025-32373

MEDIUM · 6.5 CVSS v3.1 Published 2025-04-09
Fix available
A fix is available. Upgrade to 9.13.8 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 limited configurations, registered users may be able to craft a request to enumerate/access some portal files they should not have access to. 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

DNN CMS versions before 9.13.8 contain an authorization flaw where registered users in certain limited configurations can craft HTTP requests to enumerate or access portal files outside their intended permissions. This is an authenticated access control bypass allowing unauthorized file system access within the portal.

MitigationUpgrade DNN to version 9.13.8 or later. Review portal configuration to identify if the affected limited configuration is present and verify access controls on portal file directories.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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. Determine installed DNN version
    Locate the version information for your DNN installation, typically found in the website administration panel under 'Host > About' or by inspecting the version.dll/version.txt file in the DNN installation directory
    Affected if The installed version is any version prior to 9.13.8 (e.g., 9.13.7, 9.13.0, 9.x versions below 9.13.8)
  2. Verify portal configuration for user file access settings
    Access the DNN portal settings and review the configuration options related to file uploads and downloads for registered users. Look for settings that control what directories users can access or download files from
    Affected if The portal is configured to allow registered users any form of file system access beyond their documented permissions, or uses a configuration where user permissions are not properly restricted
  3. Check registered user role permissions
    Review the permissions assigned to registered users or low-privilege user roles in the DNN role management section. Examine whether these roles have been granted access to file management modules or portal file operations
    Affected if Registered users or low-privilege roles have elevated file access capabilities enabled in the portal configuration
  4. Inspect portal file directory permissions
    Examine the file system permissions on the portal's file directories (such as the Portals/[portalID]/ folder). Verify which user roles can read, write, or list files in these directories through the web interface
    Affected if Directories outside the registered user's assigned folder are accessible or enumerable through the web application interface by authenticated users with limited privileges

Your environment is affected if you are running any DNN version before 9.13.8 and your portal configuration allows registered users to access or enumerate files beyond their intended scope.

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. Review portal configuration to identify if the affected limited configuration is present and verify access controls on portal file directories.

Recommended fix High confidence

9.13.8

  1. Create a complete backup of the DNN database and all website files
  2. Download DNN Platform version 9.13.8 from the official DNN website or GitHub releases
  3. Follow the standard DNN upgrade procedure: extract the upgrade package, stop the IIS site or application pool, upload the new files to the server, then restart the site
  4. Verify the upgrade was successful by logging into the DNN portal as an administrator
  5. Confirm the version number shows 9.13.8 in the Admin > Site Settings or Host > Host Settings area

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

Fix this in Dotnetnuke Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32373 — 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-32373 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