cve.bz

CVE-2017-0929 dnnsoftware dotnetnuke: SSRF

7.5 highEPSS 13%Fix available

High (7.5) in dnnsoftware dotnetnuke. EPSS 13% estimated probability of exploitation activity in the next 30 days. Fixed in DotNetNuke.Core 9.2.0.

On this page
DNN (aka DotNetNuke) before 9.2.0 suffers from a Server-Side Request Forgery (SSRF) vulnerability in the DnnImageHandler class. Attackers may be able to access information about internal network resources.

Severity

CVSS 3.0

7.5 high
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
13% (unchanged from 13% a week ago; 13% 30 days ago) estimated probability of exploitation activity in the next 30 days; 96th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

  • DotNetNuke.Core (NuGet): fixed in 9.2.0

Ask an AI about this CVE

Show the promptExplain CVE-2017-0929 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2017-0929?via=ask-ai-copy and https://cve.bz/cve/CVE-2017-0929?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2017-0929 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
dnnsoftware:dotnetnukebefore 9.2.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-g8j6-m4p7-5rfqNuGetDotNetNuke.Core<9.2.09.2.0

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON