Skip to content

GHSA-2rhw-gw3f-477j CVE-2026-40306

DNN: Same HostGUID for all new installs

Medium NuGet
Severity
0.0 / 10
Medium · CVSS 4.0
Exploit chance (EPSS)
0.18%
Chance of exploitation in the next 30 days. Higher than 6.97% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-330 Use of Insufficiently Random Values
Fix
10.2.2
Upgrade DotNetNuke.Core to this version or later

Description

DNN (formerly DotNetNuke) is an open-source web content management platform (CMS) in the Microsoft ecosystem. All new installations of DNN 10.x.x - 10.2.1 have the same Host GUID. This does not affect upgrades from 9.x.x. Version 10.2.2 patches the issue.

Affected versions

NuGet

PackageVulnerableFixed in
DotNetNuke.Core
>= 10.0.0, < 10.2.2
10.2.2

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

DotNetNuke.Core NuGet → 10.2.2

dotnet
dotnet add package DotNetNuke.Core --version 10.2.2

Severity breakdown

CVSS 4.0 0.0

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Attack vector
Network
Attack complexity
Low
Attack requirements
None
Privileges required
None
User interaction
None
Confidentiality (vulnerable system)
None
Integrity (vulnerable system)
Low
Availability (vulnerable system)
None
Confidentiality (subsequent systems)
None
Integrity (subsequent systems)
None
Availability (subsequent systems)
None
Exploit maturity
Not defined
Scope
X

CVSS 3.1 6.5

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

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

Weakness

CWE-330: Use of Insufficiently Random Values

The product uses insufficiently random numbers or values in a security context that depends on unpredictable numbers.

How to prevent it
  • Architecture and Design: Use a well-vetted algorithm that is currently considered to be strong by experts in the field, and select well-tested implementations with adequate length seeds. In general, if a pseudo-random number generator is not advertised as being cryptographically secure, then it is probably a statistical PRNG and should not be used in security-sensitive contexts. Pseudo-random number generators can produce predictable numbers if the generator is known and the seed can be guessed. A 256-bit seed is a good starting point for producing a "random enough" number.
  • Implementation: Consider a PRNG that re-seeds itself as needed from high quality pseudo-random output sources, such as hardware devices.
  • Architecture and Design, Requirements: Use products or modules that conform to FIPS 140-2 [REF-267] to avoid obvious entropy problems. Consult FIPS 140-2 Annex C ("Approved Random Number Generators").

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
CVE-2018-18325
Inadequate Encryption Strength in DotNetNuke
High Known exploited Also affects DotNetNuke.Core
CVE-2018-15811
Inadequate Encryption Strength in DotNetNuke
High Known exploited Also affects DotNetNuke.Core
GHSA-x2rg-fmcv-crq5
DNN (aka DotNetNuke) has Remote Code Execution via a cookie
High Known exploited Also affects DotNetNuke.Core
GHSA-fcpv-w245-r2q7
DotNetNuke.Core security code analysis rules triggered
Low Also affects DotNetNuke.Core
GHSA-fpj4-9qhx-5m6m
DNN: Force Friend Request Acceptance
Medium Also affects DotNetNuke.Core
GHSA-ffq7-898w-9jc4
DotNetNuke.Core has stored cross-site-scripting (XSS) via SVG upload
High Also affects DotNetNuke.Core
GHSA-w9pf-h6m6-v89h
DotNetNuke.Core Vulnerable to Stored XSS via Module Title
Medium Also affects DotNetNuke.Core
GHSA-vm5q-8qww-h238
DotNetNuke.Core Vulnerable to Stored XSS in Module Deletion Confirmation Modal
Medium Also affects DotNetNuke.Core
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor