Skip to content
Emerging threatsHigh

CVE-2018-15812Dotnetnuke Vulnerability

Insufficient Entropy in DotNetNuke

Published Jul 5, 2019 · Updated Jul 8, 2026 · Also known as GHSA-pf46-gqg9-j3v3

Key Facts

Patch immediately
  • CVE-2018-15812 is a high-severity vulnerability (CVSS 7.5 v3.1) affecting Dotnetnuke (Dnnsoftware), DotNetNuke.Core (nuget).
  • It is not listed in any known-exploited vulnerabilities catalog. Public exploit code is available.
  • EPSS estimates a 47% probability of exploitation in the next 30 days.
  • Fixed versions are available, including Dotnetnuke <=9.2.1, DotNetNuke.Core 9.2.2, Dotnetnuke 9.2.1.
  • Brandefense priority: patch immediately, because public exploit code exists for a high-severity flaw.

Scores

CVSS v3.1

7.5

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

EPSS (30-day exploit likelihood)

47%

Higher than 98.8% of all scored CVEs

Exploit maturity

Weaponized

ATLAS score

56/100

Publication score, see How it works

Exploitation Verdict

KEV listed

Not listed

Federal due date

None

No federal due date

Ransomware use

Not reported

Attributed actors

None named

Exploit & Defence Guidance

Exploit maturity

Weaponized

Public exploit code

2

Proof-of-concept links

In-the-wild evidence

0

Reports of active use

Advisories And Exploit References

Description

DNN (aka DotNetNuke) 9.2 through 9.2.1 incorrectly converts encryption key source values, resulting in lower than expected entropy.

Affected Products

2 affected entries in total
ProductAffected versionsFixed in
DotnetnukeDnnsoftwareSee advisory9.2.1
DotNetNuke.Corenuget>= 9.2.09.2.2

Patched Releases

Dotnetnuke

<=9.2.1

DotNetNuke.Core

9.2.2

Timeline

  1. Publicly disclosed

    Jul 5, 2019

  2. Last updated

    Jul 8, 2026

Weakness Type

  • CWE-331 Insufficient Entropy

FAQ

Common Questions.

Is CVE-2018-15812 On Your Attack Surface?

Brandefense matches it against the products discovered on your perimeter and opens a finding the day a CVE like this is listed.

Request A Demo

Figures as of Oct 19, 2026. Compiled by Brandefense technologies from public vulnerability catalogs; scoring as described in How it works.

To report an error, contact Brandefense.