dbcve.org
DotnetnukeApplication · Dnnsoftware

CVE-2025-59539

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

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, when embedding information in the Biography field, even if that field is not rich-text, users could inject javascript code that would run in the context of the website and to any other user that can view the profile including administrators and/or superusers. 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 CMS versions prior to 10.1.0 contain a stored XSS vulnerability in the user profile Biography field. Even when the field is configured as plain text (not rich-text), the application fails to properly sanitize user input, allowing injection of malicious JavaScript that executes in the browser context of any user viewing that profile, including administrators.

MitigationUpgrade to DNN version 10.1.0 or later which includes proper input sanitization for the Biography field.

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify DNN installation version
    Log into the DNN portal as Host or Administrator, navigate to Host > About or Admin > Site Settings, and locate the version number. Alternatively, open the web.config file in the website root and search for the version element in the assemblyBinding section.
    Affected if The installed version is less than 10.1.0 or equals exactly 10.1.0
  2. Verify user profile functionality is enabled
    Navigate to Admin > Site Settings > User Profile Settings (or Members > Manage User Settings in older versions). Confirm that Allow Users to Create Profile is enabled and that the profile page is accessible to users.
    Affected if User profiles are enabled and accessible to users, making the Biography field available for input
  3. Confirm Biography field exists in profile configuration
    Go to Admin > User Profile Settings > Profile Properties. Locate the Biography (or Bio) field in the list of defined profile properties and verify it is marked as Visible or Required.
    Affected if The Biography field is defined and visible in the user profile configuration
  4. Check database for existing Biography content
    Query the database table storing user profile data (typically UserProfile or similar) and retrieve rows where the PropertyName column contains 'Biography' or 'Bio'. Examine the PropertyValue column for suspicious script tags or HTML elements.
    Affected if Any Biography field entries contain unencoded HTML or script tags that could execute in a viewer's browser

A defender is affected if their DNN installation version is below 10.1.0 (or equals 10.1.0), user profiles are enabled, and the Biography field is accessible and contains unsanitized content.

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 to DNN version 10.1.0 or later which includes proper input sanitization for the Biography field.

Recommended fix High confidence

10.1.0

  1. 1. Back up your DNN database and website files before upgrading
  2. 2. Download DNN version 10.1.0 from the official DNN website or GitHub releases page
  3. 3. Follow the official DNN upgrade instructions to apply version 10.1.0 to your existing installation
  4. 4. After upgrading, verify that the Biography field properly sanitizes input and does not execute injected JavaScript
  5. 5. Test that users with different roles (including administrators) can view profiles without XSS execution

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