CVE-2026-24833
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 versions 9.13.10 and 10.2.0, a module could install with richtext in its description field which could contain scripts that will run for user 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 · high confidenceThis is a stored Cross-Site Scripting (XSS) vulnerability in DNN's Persona Bar. During module installation, the richtext description field could contain malicious JavaScript that executes when users access the Persona Bar interface. This allows attackers to inject persistent scripts that run in the context of authenticated administrator sessions.
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.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.
-
Identify installed DNN versionNavigate to Host > Host Settings in the Persona Bar, or check the Version.config file in the website root directory. The version number is displayed on the General Settings page.Affected if The installed version is less than 9.13.10, OR is 10.0.0 through 10.1.x (versions 10.2.0 and later are not affected).
-
Verify Persona Bar access existsConfirm that the DNN installation has the Persona Bar feature enabled. Log in as an administrator and attempt to access the Persona Bar menu (typically at /PersonaBar).Affected if Persona Bar is accessible and active - this is the interface where the XSS triggers when viewing module descriptions.
-
Review installed modules for custom richtext descriptionsGo to Persona Bar > Extensions > Installed Extensions. Examine each installed module's description field. Look for modules that may have been recently installed or have descriptions containing HTML script tags, javascript: URIs, or event handler attributes (onclick, onerror, onload, etc.).Affected if Any module has a description containing unescaped HTML/JavaScript that could execute when rendered in the Persona Bar interface.
-
Check database for suspicious module descriptionsQuery the Modules table or ModuleDefinitions table in the DNN database. Search the Description field for patterns like <script, javascript:, onload=, onerror=, or other XSS vectors that would not be present in legitimate module descriptions.Affected if Database contains module descriptions with encoded or raw script tags, event handlers, or JavaScript URIs.
You are affected if your DNN version falls within < 9.13.10 or >= 10.0.0 and < 10.2.0 AND you have modules installed via the Persona Bar with potentially malicious richtext descriptions that could execute JavaScript when the Persona Bar is accessed.
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 to version 9.13.10 or 10.2.0 or later, which contains input sanitization for the module description field. If immediate patching is not feasible, audit installed modules and manually review/remove any suspicious script content from module descriptions in the Persona Bar.
DNN 9.13.10 (for 9.x branch) or DNN 10.2.0 (for 10.x branch)
- 1. Back up your current DNN database and files
- 2. Review the DNN upgrade documentation for your current version
- 3. Download the appropriate fixed version (9.13.10 for 9.x branch or 10.2.0 for 10.x branch) from the official DNN repository or website
- 4. Put the site into maintenance mode or take it offline
- 5. Upload the new version files, replacing the existing installation
- 6. Run the upgrade installation following DNN's standard upgrade procedure
- 7. Clear browser cache and test the Persona Bar functionality
- 8. Verify the fix by attempting to insert script content in a module description field and confirming it does not execute
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24833 — 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-24833 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