dbcve.org
DotnetnukeApplication · Dnnsoftware

CVE-2025-59821

MEDIUM · 6.1 CVSS v3.1 Published 2025-09-23
Fix available
A fix is available. Upgrade to 10.1.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 version 10.1.0, DNN’s URL/path handling and template rendering can allow specially crafted input to be reflected into a user profile that is returned to the browser. In these cases, the application does not sufficiently neutralize or encode characters that are meaningful in HTML, so an attacker can cause a victim’s browser to interpret attacker-controlled content as part of the page’s HTML. This issue has been patched in version 10.1.0.

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 versions prior to 10.1.0 contain a stored cross-site scripting (XSS) vulnerability where user-supplied input in URL/path handling and template rendering is reflected into the user profile without proper HTML encoding, allowing attackers to inject malicious HTML/JavaScript that executes in victim browsers.

MitigationUpgrade DNN to version 10.1.0 or later to obtain the patch that properly neutralizes HTML-sensitive characters in user profile input fields.

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.0

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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
    Log into the DNN host dashboard and navigate to Host > Version or check the version via the site's footer. Alternatively, inspect the /bin/DotNetNuke.dll file version property.
    Affected if The installed version is any release prior to 10.1.0 (e.g., 10.0.x, 9.x, 8.x series).
  2. Verify user profile functionality is active
    Confirm that the DNN site has user registration and profile features enabled. Check through Admin > Site Settings > User Profile settings, or attempt to access a user profile page on the site.
    Affected if User profile pages are accessible and the profile module is loaded on the site.
  3. Inspect user profile input fields for encoding
    Create a test user or log in, navigate to the user profile edit page, and examine how the application handles special characters in profile fields like Display Name, Bio, or custom profile properties.
    Affected if The application accepts HTML or script-capable input in profile fields without visible sanitization feedback or encoding.

Your environment is affected if the installed DNN version is below 10.1.0 and user profile functionality is enabled on the site.

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.0 or later
Fixed in 10.1.0
Interim mitigation

Upgrade DNN to version 10.1.0 or later to obtain the patch that properly neutralizes HTML-sensitive characters in user profile input fields.

Recommended fix High confidence

DNN 10.1.0

  1. 1. Create a complete backup of the DNN database and all website files
  2. 2. Download DNN version 10.1.0 from the official DNN repository or website
  3. 3. Extract the downloaded package contents to the web server document root
  4. 4. Ensure the web.config file from the backup is preserved or merged as needed
  5. 5. Run the upgrade by accessing the website - DNN will automatically detect and apply the upgrade
  6. 6. Clear any caching systems (application restart, CDN caches) after upgrade
  7. 7. Verify the installation by logging in as host/admin and checking the version number
  8. 8. Test that the URL/path handling and profile rendering work correctly
Caveat Review DNN 10.1.0 release notes for any breaking changes or migration considerations before upgrading

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

Fix this in Dotnetnuke Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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