CVE-2018-15811
Crypto Weakness in Dnnsoftware Dotnetnuke 9.2 – 9.2.1
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
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.5% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog; a public proof-of-concept is referenced.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
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.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2019-0590
Vulnerability Data
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
CVEs Like This One
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Maintaining currency with technologies and practices reduces selection of encryption mechanisms that provide inadequate strength.
Updated assessments identify when previously adequate encryption strength no longer meets current attack capabilities or compliance drivers.
Establishment procedures require selection and generation of keys with adequate length and strength for the chosen algorithm.
Specifies required cryptography types and parameters, preventing selection of inadequate encryption strength.
Prompt patching corrects inadequate encryption strength when vendors release updates that increase key sizes or algorithm security.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Requiring the organization to define and enforce minimum cryptographic strength prevents deployment of insufficient key lengths or weak ciphers that can be brute-forced.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-326, a class-level weakness. Rules are authored against its narrower children: CWE-328.