CVE-2026-24836
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. Starting in version 9.0.0 and prior to versions 9.13.10 and 10.2.0, extensions could write richtext in log notes which can include scripts that would run in the PersonaBar when displayed. 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 · high confidenceThis is a stored XSS (Cross-Site Scripting) vulnerability in DNN CMS where extensions can write richtext content containing malicious JavaScript into log notes. When these log notes are displayed in the PersonaBar administrative interface, the embedded scripts execute in the browser context of authenticated administrators.
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>= 9.0.0, < 9.13.10>= 10.0.0, < 10.2.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed DNN versionLog into the DNN site as an administrator and navigate to PersonaBar > Settings > Site Settings to view the version information. Alternatively, check the version.txt file in the website root directory if accessible through file system.Affected if The installed version is >= 9.0.0 and < 9.13.10, or >= 10.0.0 and < 10.2.0
-
Verify PersonaBar administrative interface is enabledCheck if the PersonaBar is accessible by logging in as an administrator and attempting to access PersonaBar features. Inspect the web.config file for PersonaBar module configurations.Affected if PersonaBar is enabled and accessible to authenticated administrators
-
Identify extensions writing richtext to log notesReview installed extensions and modules. Check the database for any entries in log-related tables (such as EventLog or similar logging tables) that contain richtext or HTML content in note fields.Affected if Any extension writes richtext content to log notes that are displayed in PersonaBar
The environment is affected if the DNN version is within the vulnerable ranges and extensions that write richtext content to log notes are in use, with those notes viewable through PersonaBar.
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 · scoped9.13.1010.2.0
Upgrade DNN installations to version 9.13.10 or 10.2.0 which contain the fix for proper input sanitization of richtext in log notes.
Upgrade to DNN version 9.13.10 (for 9.x branch) or version 10.2.0 (for 10.x branch)
- Backup the entire DNN website database and file system before proceeding with any upgrade
- Ensure your current DNN installation is functioning properly before upgrading
- Download the appropriate upgrade package for your version path: version 9.13.10 for 9.x installations or version 10.2.0 for 10.x installations
- Review DNN upgrade documentation for your specific version path
- Execute the upgrade by running the upgrade package on your staging environment first
- Verify all extensions and modules function correctly after upgrade
- Deploy the upgraded version to production after successful staging validation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24836 — 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-2026-24836 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