Threats / DotNetNuke (DNN) / CVE-2018-18325
CVE-2018-18325
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-19
DotNetNuke (DNN) vulnerability
DotNetNuke contains inadequate encryption strength in input parameter protection due to use of weak encryption algorithms. This resolves an incomplete patch for CVE-2018-15811.
Verdict
Today item — known-exploited.
Weak encryption of input parameters in DotNetNuke allows attackers to potentially decrypt or manipulate protected data. Active exploitation in the wild combined with high EPSS score indicates significant risk despite incomplete patch history.
CISA KEV Yes · 2021-11-034EPSS 0.74048 (verify live)5CVSS 7.5 (CISA)3CISA SSVC Exploitation: active · Automatable: yes · Impact: partial3Exploit Weaponized · public exploit · Metasploit module · nuclei template8
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
1 independent public report of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03).
Probability (EPSS)
EPSS 0.74048 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) · Affected: DotNetNuke (DNN), DotNetNuke (DNN). Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-326 Inadequate Encryption Strength — weakness family: Cryptography.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: partialCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 854 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module, nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I identify that DotNetNuke uses weak encryption algorithms to protect input parameters.
Business
Sensitive input data lacks adequate cryptographic protection, creating exposure of user information and application logic.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I decrypt or reverse-engineer the weak encryption to recover plaintext input parameters.
Business
Confidentiality of user submissions, authentication tokens, and configuration data is compromised.
3
Lateral reach — past segmentation narrative 3
Attacker
I modify encrypted parameters to inject malicious input or escalate privileges within the application.
Business
Application integrity is undermined, enabling unauthorized access, data manipulation, or administrative compromise.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by mitreCNA
Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.