Cross-Site Scripting (XSS) in Dnnsoftware (CVE-2025-64094)
Summary
Cross-site scripting in Dnnsoftware (CVE-2025-64094). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 10.1.1 or later.
Original description
The description as published by the source.
DNN (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.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-64094 has been found in Dnnsoftware.
Risk of unauthorized operations or information disclosure. CVSS score: 6.4/10.
What to do: upgrade Dnnsoftware to 10.1.1 or later.
If unsure, ask your IT team or search "Dnnsoftware CVE-2025-64094" on the vendor's site.
CVE-2025-64094 (Dnnsoftware) — CWE-79 / CVSS v3 6.4
Attack vector: remote (network-reachable) / no user interaction
Patched: 10.1.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Cross-site scripting (XSS) (CWE-79) exists in Dnnsoftware.
Check the vendor advisory for the affected versions of Dnnsoftware.
Severity: Medium (CVSS 6.4/10). Risk of unauthorized operations or information disclosure.
Update to 10.1.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Dnnsoftware' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Dnnsoftware' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Dnnsoftwareを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Dnnsoftware to 10.1.1ステージング環境で 10.1.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。