Unrestricted File Upload in Dnnsoftware (CVE-2025-62802)
Summary
Vulnerability in Dnnsoftware (CVE-2025-62802). 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, the out-of-box experience for HTML editing allows unauthenticated users to upload files. This opens a potential vector to other security issues and is not needed on most implementations. 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-62802 has been found in Dnnsoftware.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade Dnnsoftware to 10.1.1 or later.
If unsure, ask your IT team or search "Dnnsoftware CVE-2025-62802" on the vendor's site.
CVE-2025-62802 (Dnnsoftware) — CWE-434 / CVSS v3 4.3
Attack vector: remote (network-reachable) / unauthenticated
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.
A vulnerability (CWE-434) exists in Dnnsoftware.
Check the vendor advisory for the affected versions of Dnnsoftware.
Severity: Medium (CVSS 4.3/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 でアラート再発が無いか継続監視。