CVE-2025-64094
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 10.1.1, sanitization of the content of uploaded SVG files was not covering all possible XSS scenarios. This vulnerability exists because of an incomplete fix for CVE-2025-48378. This vulnerability is fixed in 10.1.1.
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 confidenceDNN CMS versions prior to 10.1.1 contain an incomplete sanitization of SVG file uploads that allows XSS attacks. The vulnerability stems from an incomplete fix for CVE-2025-48378, where not all XSS vectors in SVG content were properly neutralized during upload processing.
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.1CVSS 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 DNN installation versionLocate the version information in the DNN installation, typically found in the Site Settings, in the web.config file, or by checking the DLL assembly version in the /bin folderAffected if The installed version is any version prior to 10.1.1 (e.g., 10.1.0, 9.x, 8.x, etc.)
-
Verify if SVG upload functionality is availableCheck whether the File Upload or Assets module in DNN is accessible to users and allows SVG file types to be uploaded. This may be confirmed by attempting a test upload with an SVG file or reviewing the allowed file extensions in the Host settingsAffected if SVG file uploads are permitted in the CMS and users have upload permissions
-
Confirm the upload module is exposed to potentially malicious usersReview user role permissions to determine if untrusted or low-privilege users can access file upload features. Check whether the Assets or File Manager module is visible to non-admin usersAffected if Users with limited privileges (e.g., registered users, content editors) can access and use the file upload functionality
-
Inspect uploaded SVG handling behaviorUpload a test SVG file containing a script tag or event handler (e.g., <script>alert(1)</script> or onload=) and verify whether the CMS executes or persists the malicious content when the file is accessedAffected if The uploaded SVG file is stored and served in a way that executes JavaScript or renders the injected markup when viewed
User is affected if running DNN version below 10.1.1 AND the SVG upload feature is accessible to users who could inject malicious scripts.
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.1
Upgrade to DNN 10.1.1 or later to apply the complete fix. As a temporary measure, block or restrict SVG file uploads at the web server level until the upgrade can be performed.
DNN 10.1.1
- 1. Back up your existing DNN installation and database before proceeding with any upgrade
- 2. Review the official DNN 10.1.1 release notes and migration documentation
- 3. Upgrade your DNN installation to version 10.1.1 following the official upgrade instructions
- 4. After upgrade, verify that the application runs correctly
- 5. Test SVG file upload functionality to confirm the XSS sanitization is working properly
- 6. Monitor the DNN application for any unexpected behavior after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64094 — 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-64094 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