CVE-2025-59545
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 · uneditedDNN (formerly DotNetNuke) is an open-source web content management platform (CMS) in the Microsoft ecosystem. Prior to version 10.1.0, the Prompt module allows execution of commands that can return raw HTML. Malicious input, even if sanitized for display elsewhere, can be executed when processed through certain commands, leading to potential script execution (XSS). 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 confidenceThe Prompt module in DNN (DotNetNuke) versions prior to 10.1.0 contains a cross-site scripting (XSS) vulnerability. Certain commands in the Prompt module return raw HTML, and malicious input that has been sanitized for display elsewhere can still be executed when processed through these specific commands, allowing script execution in user browsers.
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< 10.1.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify DNN installation versionLocate the version file or check the website footer/admin panel for the installed DNN version number. Common locations include the ~/Version.txt file or the Admin > About page in the DNN dashboard.Affected if The version is below 10.1.0
-
Confirm Prompt module is presentCheck if the Prompt module is installed by reviewing the installed modules list in Host > Extensions or by examining the /DesktopModules/Prompt directory on the web server.Affected if The Prompt module exists in the installation
-
Verify Prompt module is enabledCheck if the Prompt feature is activated for any portal by reviewing the module definitions in Host > Extensions or checking if the Prompt command console is accessible on the site.Affected if The Prompt module is installed and active on one or more portals
-
Identify commands that return raw HTMLReview the Prompt module command handlers in the ~/DesktopModules/Prompt folder for commands that output unencoded HTML content, particularly those that accept user input and render it back without encoding.Affected if Commands that return raw HTML are present and accessible to users
-
Test for XSS execution via PromptUse the Prompt console (if accessible) to input a test XSS payload such as <script>alert('test')</script> through commands that render input back as HTML, observing whether the script executes in the browser.Affected if The malicious payload executes as JavaScript in the browser rather than being displayed as harmless text
A user is affected if they are running DNN version below 10.1.0 with the Prompt module enabled and accessible to users who can execute commands that return raw HTML to the browser.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.1.0
Upgrade DNN to version 10.1.0 or later to obtain the patch for this vulnerability.
10.1.0
- Back up the existing DNN database and all website files
- Download DNN version 10.1.0 from the official DNN website or GitHub releases
- Review the DNN upgrade documentation for any specific pre-upgrade requirements
- Place the site in maintenance mode or take offline
- Extract and deploy the 10.1.0 files to the web server, overwriting existing files
- Run the upgrade installation by accessing the site
- Verify the Prompt module functions correctly post-upgrade
- Remove any maintenance mode and test thoroughly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59545 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-59545 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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