How severe is GHSA-m4hf-fxcg-cp34?

No CVSS score has been assigned to GHSA-m4hf-fxcg-cp34 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-m4hf-fxcg-cp34?

GHSA-m4hf-fxcg-cp34 affects the following packages: DotNetNuke.Core (NuGet). Ecosystems affected: NuGet.

How do I fix GHSA-m4hf-fxcg-cp34?

Update DotNetNuke.Core to 9.13.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m4hf-fxcg-cp34 is resolved across your whole dependency graph.

How do I detect GHSA-m4hf-fxcg-cp34 in my NuGet dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for DotNetNuke.Core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-m4hf-fxcg-cp34 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-m4hf-fxcg-cp34?

O3 pinpoints whether GHSA-m4hf-fxcg-cp34 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-m4hf-fxcg-cp34 actively exploited in the wild?

No public exploit code has been indexed for GHSA-m4hf-fxcg-cp34 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-m4hf-fxcg-cp34?

GHSA-m4hf-fxcg-cp34 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 15th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-m4hf-fxcg-cp34?

GHSA-m4hf-fxcg-cp34 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-m4hf-fxcg-cp34 published, and has it been updated?

GHSA-m4hf-fxcg-cp34 was published on May 23, 2025 and was last updated on May 23, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET NuGet

GHSA-m4hf-fxcg-cp34

DNN allows Stored Cross-Site Scripting (XSS) with svg files rendered inline

Also known asCVE-2025-48378

Published

May 23, 2025

Updated

May 23, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk15th percentile+0.19%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

.NETDotNetNuke.Core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

Uploaded SVG files could contain scripts and if rendered inline those scripts could run allowing XSS attacks.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`DotNetNuke.Core`	all versions	9.13.9

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for DotNetNuke.Core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update DotNetNuke.Core to 9.13.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m4hf-fxcg-cp34 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-m4hf-fxcg-cp34 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-m4hf-fxcg-cp34. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Uploaded SVG files could contain scripts and if rendered inline those scripts could run allowing XSS attacks.

O3 Security · Impact-Aware SCA

Is GHSA-m4hf-fxcg-cp34 in your dependencies?

O3 detects GHSA-m4hf-fxcg-cp34 across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works