Skip to content

GHSA-3f7v-qx94-666m CVE-2025-32372

DotNetNuke.Core Vulnerable to Server-Side Request Forgery (SSRF)

High NuGet
Severity
6.5 / 10
High · CVSS 3.1
Exploit chance (EPSS)
0.38%
Chance of exploitation in the next 30 days. Higher than 31.94% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-918 Server-Side Request Forgery (SSRF)
Fix
9.13.8
Upgrade DotNetNuke.Core to this version or later

Description

A bypass has been identified for the previously known vulnerability CVE-2017-0929, allowing unauthenticated attackers to execute arbitrary GET requests against target systems, including internal or adjacent networks.

Impact

This vulnerability facilitates a semi-blind SSRF attack, allowing attackers to make the target server send requests to internal or external URLs without viewing the full responses. Potential impacts include internal network reconnaissance, bypassing firewalls.

Affected versions

NuGet

PackageVulnerableFixed in
DotNetNuke.Core
< 9.13.8
9.13.8

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

DotNetNuke.Core NuGet → 9.13.8

dotnet
dotnet add package DotNetNuke.Core --version 9.13.8

Severity breakdown

CVSS 3.1 6.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

Weakness

CWE-918: Server-Side Request Forgery (SSRF)

The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
CVE-2018-18325
Inadequate Encryption Strength in DotNetNuke
High Known exploited Also affects DotNetNuke.Core
CVE-2018-15811
Inadequate Encryption Strength in DotNetNuke
High Known exploited Also affects DotNetNuke.Core
GHSA-x2rg-fmcv-crq5
DNN (aka DotNetNuke) has Remote Code Execution via a cookie
High Known exploited Also affects DotNetNuke.Core
GHSA-fcpv-w245-r2q7
DotNetNuke.Core security code analysis rules triggered
Low Also affects DotNetNuke.Core
GHSA-2rhw-gw3f-477j
DNN: Same HostGUID for all new installs
Medium Also affects DotNetNuke.Core
GHSA-fpj4-9qhx-5m6m
DNN: Force Friend Request Acceptance
Medium Also affects DotNetNuke.Core
GHSA-ffq7-898w-9jc4
DotNetNuke.Core has stored cross-site-scripting (XSS) via SVG upload
High Also affects DotNetNuke.Core
GHSA-w9pf-h6m6-v89h
DotNetNuke.Core Vulnerable to Stored XSS via Module Title
Medium Also affects DotNetNuke.Core
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor