Skip to content
Fencer Intel
high 7.5

CVE-2018-18325 kev in the critical feed json

Inadequate Encryption Strength in DotNetNuke

published 7y ago modified 4mo ago also GHSA-j3g9-6fx5-gjv7 , EUVD-2019-0595

cvss
7.5
version 3.1, CNA
cisa kev
Exploited
added 2021-11-03
epss
74.0%
EPSS 74.0% chance of exploitation in 30 days, percentile 99.4%
public exploits
2
Metasploit and Exploit-DB, plus a Nuclei check

Summary

DNN (aka DotNetNuke) 9.2 through 9.2.2 uses a weak encryption algorithm to protect input parameters. NOTE: this issue exists because of an incomplete fix for CVE-2018-15811.

Patch / fix

cisa required action Apply updates per vendor instructions.

  • nuget DotNetNuke.Core 9.3.0

Is CVE-2018-18325 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. First public exploit (Metasploit exploit/windows/http/dnn_cookie_deserialization_rce)
  2. Published
  3. Added to CISA KEV
  4. CISA patch deadline
  5. CISA SSVC: exploitation active

Known exploited

Added
5y ago
Patch by
2022-05-03 (4y ago)
Ransomware
Not known
Required action
Apply updates per vendor instructions.
Vendor, product
DotNetNuke (DNN), DotNetNuke (DNN)
CISA name
DotNetNuke (DNN) Inadequate Encryption Strength Vulnerability

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
yes
Technical impact
partial
Assessed
last yr.

Exploit prediction

74.05% chance of exploitation in the next 30 days, higher than 99.4% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

CVSS scores

assigned by version score vector
CISA ADP 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N
GitHub 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N/E:H

Affected packages

ecosystem package affected fixed in
nuget DotNetNuke.Core
<9.3.0
9.3.0

Classification

Weakness
  • CWE-326 Inadequate Encryption Strength

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.