dbcve.org
DotnetnukeApplication · Dnnsoftware

CVE-2026-24837

MEDIUM · 5.4 CVSS v3.1 Published 2026-01-28
Fix available
A fix is available. Upgrade to 9.13.10 / 10.2.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. Starting in version 9.0.0 and prior to versions 9.13.10 and 10.2.0, a module friendly name could include scripts that will run during some module operations in the Persona Bar. Versions 9.13.10 and 10.2.0 contain a fix for the issue.

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

This is a stored Cross-Site Scripting (XSS) vulnerability in DNN's Persona Bar. Attackers can inject malicious JavaScript into a module's friendly name field, which executes when administrators perform certain module operations in the Persona Bar interface.

MitigationUpgrade DNN to version 9.13.10, 10.2.0, or later to resolve the XSS vulnerability in module friendly name handling.

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.0.0, < 9.13.10>= 10.0.0, < 10.2.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 installed DNN version
    Check the version file or navigate to Host > About in the DNN admin interface. The version is typically stored in a version.txt or displayed in the Persona Bar under Settings > About.
    Affected if The installed version falls within >= 9.0.0 and < 9.13.10, or >= 10.0.0 and < 10.2.0
  2. Confirm Persona Bar is accessible
    Log in as an administrator and verify access to the Persona Bar interface (the icon in the left sidebar). The vulnerability affects module operations performed through this interface.
    Affected if Persona Bar is enabled and accessible to admin users in the environment
  3. Review module friendly name settings
    Navigate to Persona Bar > Pages > Edit Modules, or go to the module configuration panel where friendly names are defined. Inspect the friendly name field for any modules installed in the site.
    Affected if A module friendly name contains unsanitized or unexpected content that was not entered by an administrator, indicating potential injection
  4. Check module configuration files
    Inspect the modules table in the database or the module definition files in the /DesktopModules directory for any friendly_name values that appear unusual or contain script tags.
    Affected if Module friendly name values in the database or configuration contain HTML or JavaScript characters such as <script>, javascript:, or event handlers

A user is affected if the DNN installation version is within the vulnerable ranges AND the Persona Bar interface is in use, with potentially injected content present in module friendly name fields.

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.10 / 10.2.0 or later
Fixed in 9.13.1010.2.0
Interim mitigation

Upgrade DNN to version 9.13.10, 10.2.0, or later to resolve the XSS vulnerability in module friendly name handling.

Recommended fix High confidence

9.13.10 (for 9.x branches) or 10.2.0 (for 10.x branches)

  1. 1. Backup your current DNN installation and database
  2. 2. Review DNN upgrade documentation for your current version
  3. 3. Download the appropriate fixed version (9.13.10 for 9.x line or 10.2.0 for 10.x line) from the official DNN repository
  4. 4. Test the upgrade in a staging environment first
  5. 5. Execute the upgrade following standard DNN upgrade procedures
  6. 6. Verify the fix by confirming module operations in Persona Bar no longer execute arbitrary scripts
Caveat Major DNN upgrades may require testing of custom modules, skins, and extensions for compatibility

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
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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