CVE-2025-52488VulnerabilityPublished 21 Jun 2025Updated 23 Jun 2025

CVE-2025-52488: dnnsoftware Dnn.Platform · Information Exposure

Affects dnnsoftware Dnn.PlatformSource CVE Database V5

Not known to be exploited · public detection template (Nuclei) · 35% EPSS · CVSS 8.6 High : upgrade to 10.0.1 soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

8.6High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 35.7% chance of exploitation in 30 days – higher than 98% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 10.0.1

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Jun 2025
Detectable: evidence found.
nuclei template: DNN (DotNetNuke) - Unicode Path Normalization NTLM Hash Disclosure
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade dnnsoftware Dnn.Platform to 10.0.1.

Affected software

Product	Affected	Fixed in
NuGetdnn.platform`pkg:nuget/dnn.platform`Other threats	Affected <10.0.1 >=6.0.0	Fixed in 10.0.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediate upgrade of all Dnn.Platform instances to version 10.0.1 or later, where the vulnerability is patched, is the most effective mitigation. 2. For environments where immediate upgrade is not feasible, implement network-level controls to restrict outbound SMB traffic from web servers hosting Dnn.Platform, preventing NTLM hash leakage to unauthorized SMB servers. 3. Employ network segmentation to isolate web servers from sensitive internal networks, limiting lateral movement opportunities if credentials are compromised. 4. Monitor network traffic for unusual SMB connection attempts or unexpected outbound SMB traffic from web servers, using IDS/IPS or network monitoring tools. 5. Enforce strong password policies and consider disabling NTLM authentication where possible in favor of more secure protocols like Kerberos. 6. Conduct regular audits of Dnn.Platform versions across the organization to identify and remediate outdated instances. 7. Implement multi-factor authentication (MFA) for all critical systems to reduce the impact of credential compromise. 8. Educate IT and security teams about this vulnerability and ensure incident response plans include steps for potential NTLM hash exposure incidents. 9. Review and harden SMB server configurations to prevent unauthorized SMB connections and limit exposure to relay attacks. 10. Apply principle of least privilege to service accounts and users interacting with Dnn.Platform to minimize potential damage from compromised credentials.

Description

DNN (formerly DotNetNuke) is an open-source web content management platform (CMS) in the Microsoft ecosystem. In versions 6.0.0 to before 10.0.1, DNN.PLATFORM allows a specially crafted series of malicious interaction to potentially expose NTLM hashes to a third party SMB server. This issue has been patched in version 10.0.1.

Impact

For European organizations, the exposure of NTLM hashes poses a substantial risk, particularly for enterprises and public sector entities that utilize Dnn.Platform for web content management. Successful exploitation could lead to credential compromise, enabling attackers to impersonate legitimate users, escalate privileges, and move laterally within corporate networks. This can result in unauthorized access to sensitive data, disruption of business processes, and potential regulatory non-compliance under GDPR due to data breaches. Organizations relying on NTLM authentication are especially vulnerable, as compromised hashes can facilitate relay attacks or offline cracking. The impact is magnified in sectors with high-value targets such as finance, government, healthcare, and critical infrastructure, where unauthorized access could lead to significant operational and reputational damage. Additionally, the vulnerability’s network-based exploitation vector means that external attackers can attempt to exploit internet-facing Dnn.Platform instances, increasing the attack surface. The lack of known exploits in the wild currently provides a window for remediation, but the high CVSS score and ease of exploitation suggest that threat actors may develop exploits rapidly. Failure to patch could lead to widespread compromise, especially in environments where patch management is slow or where legacy versions of Dnn.Platform are still in use.

CWE-200Exposure of Sensitive Information to an Unauthorized Actor (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #20OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Subverting Environment Variable Values (opens in a new tab)
ICMP Echo Request Ping (opens in a new tab)
TCP SYN Scan (opens in a new tab)
Enumerate Mail Exchange (MX) Records (opens in a new tab)
DNS Zone Transfers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/dnnsoftware/Dnn.Platform/security/advisories/GHSA-mgfv-2362-jq96 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Jun 2025, 11:51 UTC

Public exploits and detectiona Nuclei detection template

WeaknessesCWE-200

Technical details

References

Community reviews

Related threats