Cyber Resilience

CVE-2018-15811

HighCISA KEVActive ExploitationEUVD ExploitedPublic PoC

Published: 03 July 2019

Published
03 July 2019
Modified
07 November 2025
KEV Added
03 November 2021
Patch
CVSS Score v3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.9296 99.8th percentile
Risk Priority 91 60% EPSS · 20% KEV · 20% CVSS

Summary

CVE-2018-15811 is a high-severity Inadequate Encryption Strength (CWE-326) vulnerability in Dnnsoftware Dotnetnuke. Its CVSS base score is 7.5 (High).

Operationally, ranked in the top 0.2% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified are NIST 800-53 SC-13 (Cryptographic Protection) and SC-8 (Transmission Confidentiality and Integrity).

Deeper analysis

DNN (also known as DotNetNuke) versions 9.2 through 9.2.1 are affected by a vulnerability that stems from use of a weak encryption algorithm to protect input parameters, corresponding to CWE-326. The issue carries a CVSS 3.1 base score of 7.5, reflecting a network-accessible flaw with low attack complexity that requires no privileges or user interaction and results in high confidentiality impact.

An unauthenticated attacker can supply crafted input parameters protected only by the weak algorithm, potentially allowing recovery of sensitive data or further abuse such as cookie deserialization leading to remote code execution.

Public exploit material referencing cookie deserialization remote code execution has been published, and official advisories along with patches are referenced in the DNN security center and the project's GitHub releases.

EU & UK References

Vulnerability details

DNN (aka DotNetNuke) 9.2 through 9.2.1 uses a weak encryption algorithm to protect input parameters.

CWE(s)
KEV Date Added
03 November 2021

Related Threats

No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.

Affected Assets

dnnsoftware
dotnetnuke
9.2 — 9.2.1

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly requires use of approved cryptographic algorithms, preventing the weak encryption of input parameters that enables the described decryption and RCE attacks.

prevent

Enforces cryptographic protection of transmitted data confidentiality and integrity, mitigating exposure of weakly-encrypted input parameters or cookies.

prevent

Requires timely remediation of known flaws, directly addressing application of the published DNN patches that correct the weak-algorithm implementation.

References