CVE-2018-15811

HIGHNVD 7.59.0
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.5 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, nvd
Trending — 3 sources updated this weekExploited in the wild
7.5
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 74%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

CVSS v3
7.5
EG Score
9.0(high)
EG Risk
96(Attend)
EG Risk 96/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation100% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS
99.4%
KEV
⚠ Exploited

Published

July 3, 2019

Last Modified

November 7, 2025

Advisory Details (3)

Auto-updated Jun 6, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: cisa.
cisa Patch Available🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2018-15811
generic

Releases · dnnsoftware/Dnn.Platform · GitHub

https://github.com/dnnsoftware/Dnn.Platform/releases

Affected Packages

(1 across 1 ecosystem)
NuGet(1)
PackageVulnerable rangeFixed inDependents
DotNetNuke.Core9.2.0.366, 9.2.1.5339.2.2

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 20× in last 7d / 47× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 01:34 UTCEG score recompute
  2. 2026-07-23 00:07 UTCEG score recompute
  3. 2026-07-22 22:14 UTCEG score recompute
  4. 2026-07-22 19:40 UTCCISA KEV update
  5. 2026-07-22 16:15 UTCEG score recompute
  6. 2026-07-22 14:04 UTCEPSS rescore
  7. 2026-07-21 16:01 UTCEG score recompute
  8. 2026-07-21 15:21 UTCEPSS rescore
  9. 2026-07-21 14:37 UTCCISA KEV update
  10. 2026-07-20 20:17 UTCEG score recompute
  11. 2026-07-20 17:04 UTCEPSS rescore
  12. 2026-07-20 17:04 UTCEPSS rescore
  13. 2026-07-19 16:45 UTCEG score recompute
  14. 2026-07-19 14:28 UTCEPSS rescore
  15. 2026-07-19 04:58 UTCEG score recompute
  16. 2026-07-19 02:26 UTCEPSS rescore
  17. 2026-07-19 02:26 UTCEPSS rescore
  18. 2026-07-18 13:13 UTCEG score recompute
  19. 2026-07-17 09:46 UTCEG score recompute
  20. 2026-07-16 17:04 UTCCISA KEV update
  21. 2026-07-15 16:55 UTCEPSS rescore
  22. 2026-07-15 16:49 UTCCISA KEV update
  23. 2026-07-15 15:04 UTCCISA KEV update
  24. 2026-07-14 18:05 UTCCISA KEV update
  25. 2026-07-13 22:26 UTCEPSS rescore
Show 62 more
  1. 2026-07-13 17:07 UTCCISA KEV update
  2. 2026-07-11 08:24 UTCEPSS rescore
  3. 2026-07-10 17:52 UTCCISA KEV update
  4. 2026-07-08 15:11 UTCEPSS rescore
  5. 2026-07-07 19:01 UTCCISA KEV update
  6. 2026-07-07 17:16 UTCCISA KEV update
  7. 2026-07-04 06:28 UTCEPSS rescore
  8. 2026-07-01 19:16 UTCCISA KEV update
  9. 2026-07-01 15:03 UTCEPSS rescore
  10. 2026-07-01 15:03 UTCEPSS rescore
  11. 2026-06-30 23:19 UTCEPSS rescore
  12. 2026-06-30 23:19 UTCEPSS rescore
  13. 2026-06-29 19:12 UTCCISA KEV update
  14. 2026-06-28 14:04 UTCEPSS rescore
  15. 2026-06-28 04:53 UTCEPSS rescore
  16. 2026-06-28 04:53 UTCEPSS rescore
  17. 2026-06-27 03:06 UTCEPSS rescore
  18. 2026-06-25 19:15 UTCCISA KEV update
  19. 2026-06-24 14:02 UTCEPSS rescore
  20. 2026-06-24 14:02 UTCEPSS rescore
  21. 2026-06-23 21:30 UTCEPSS rescore
  22. 2026-06-23 17:44 UTCCISA KEV update
  23. 2026-06-21 14:54 UTCEPSS rescore
  24. 2026-06-21 14:54 UTCEPSS rescore
  25. 2026-06-18 17:50 UTCEPSS rescore
  26. 2026-06-18 17:50 UTCEPSS rescore
  27. 2026-06-18 16:13 UTCCISA KEV update
  28. 2026-06-16 19:33 UTCCISA KEV update
  29. 2026-06-16 17:50 UTCEPSS rescore
  30. 2026-06-16 17:50 UTCEPSS rescore
  31. 2026-06-15 19:33 UTCCISA KEV update
  32. 2026-06-15 17:45 UTCEPSS rescore
  33. 2026-06-12 17:35 UTCCISA KEV update
  34. 2026-06-11 19:10 UTCCISA KEV update
  35. 2026-06-09 18:42 UTCCISA KEV update
  36. 2026-06-09 17:12 UTCCISA KEV update
  37. 2026-06-08 19:16 UTCCISA KEV update
  38. 2026-06-08 17:26 UTCCISA KEV update
  39. 2026-06-08 14:14 UTCEPSS rescore
  40. 2026-06-08 14:14 UTCEPSS rescore
  41. 2026-06-05 22:45 UTCEPSS rescore
  42. 2026-06-05 22:44 UTCEPSS rescore
  43. 2026-06-05 22:43 UTCCISA KEV update
  44. 2026-06-04 13:10 UTCEPSS rescore
  45. 2026-06-04 13:10 UTCEPSS rescore
  46. 2026-06-03 19:09 UTCCISA KEV update
  47. 2026-06-02 18:32 UTCCISA KEV update
  48. 2026-06-01 20:42 UTCCISA KEV update
  49. 2026-05-31 22:29 UTCEPSS rescore
  50. 2026-05-31 22:28 UTCEPSS rescore
  51. 2026-05-29 22:20 UTCCISA KEV update
  52. 2026-05-29 13:41 UTCEPSS rescore
  53. 2026-05-28 13:42 UTCEPSS rescore
  54. 2026-05-28 13:42 UTCEPSS rescore
  55. 2026-05-27 20:35 UTCCISA KEV update
  56. 2026-05-27 13:38 UTCEPSS rescore
  57. 2026-05-27 13:38 UTCEPSS rescore
  58. 2026-05-26 19:20 UTCEG score recompute
  59. 2026-05-26 19:13 UTCCISA KEV update
  60. 2026-05-26 07:17 UTCEPSS rescore
  61. 2026-05-26 07:17 UTCEPSS rescore
  62. 2026-05-23 04:35 UTCOSV refresh

Publicly available exploits

(3 references)

Working exploit code is in the public domain (1 Metasploit module) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-48336✓ verified
    First seen Apr 16, 2020

    DotNetNuke - Cookie Deserialization Remote Code Execution (Metasploit)

    Open source ↗
  • Nucleihttp/cves/2018/CVE-2018-15811.yaml
    First seen Jan 1, 2018

    DotNetNuke 9.2 - 9.2.1 - Weak Encryption & Cookie Deserialization

    Open source ↗
  • Metasploitexploit/windows/http/dnn_cookie_deserialization_rce✓ verified
    First seen Jul 20, 2017

    DotNetNuke Cookie Deserialization Remote Code Excecution

    Open source ↗

Frequently asked(6)

What is CVE-2018-15811?
CVE-2018-15811 is a high vulnerability published on July 3, 2019. DNN (aka DotNetNuke) 9.2 through 9.2.1 uses a weak encryption algorithm to protect input parameters.
When was CVE-2018-15811 disclosed?
CVE-2018-15811 was first published in the National Vulnerability Database on July 3, 2019, with the most recent update on November 7, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-15811 actively exploited?
Yes. CISA added CVE-2018-15811 to the Known Exploited Vulnerabilities catalog on November 3, 2021, affecting DotNetNuke (DNN) DotNetNuke (DNN). KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2018-15811?
CVE-2018-15811 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
Which products are affected by CVE-2018-15811?
CVE-2018-15811 affects DotNetNuke (DNN) DotNetNuke (DNN). The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2018-15811?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-15811, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2018-15811

Explore →

Is Your Infrastructure Affected by CVE-2018-15811?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.