How severe is GHSA-vm5q-8qww-h238?

GHSA-vm5q-8qww-h238 has a CVSS score of 7.6/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-vm5q-8qww-h238?

GHSA-vm5q-8qww-h238 affects the following packages: DotNetNuke.Core (NuGet), DotNetNuke.Core (NuGet). Ecosystems affected: NuGet.

How do I fix GHSA-vm5q-8qww-h238?

No patched version of DotNetNuke.Core has shipped for GHSA-vm5q-8qww-h238 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-vm5q-8qww-h238 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-vm5q-8qww-h238 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-vm5q-8qww-h238?

O3 pinpoints whether GHSA-vm5q-8qww-h238 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-vm5q-8qww-h238 actively exploited in the wild?

No public exploit code has been indexed for GHSA-vm5q-8qww-h238 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 type of vulnerability is GHSA-vm5q-8qww-h238?

GHSA-vm5q-8qww-h238 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-vm5q-8qww-h238 published, and has it been updated?

GHSA-vm5q-8qww-h238 was published on January 28, 2026 and was last updated on February 3, 2026. 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-vm5q-8qww-h238

HIGH

GHSA-vm5q-8qww-h238 is a high-severity (CVSS 7.6) Cross-site Scripting (XSS) vulnerability in DotNetNuke.Core. O3 Security confirms whether GHSA-vm5q-8qww-h238 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

DotNetNuke.Core Vulnerable to Stored XSS in Module Deletion Confirmation Modal

Also known asCVE-2026-24837

Published

Jan 28, 2026

Updated

Feb 3, 2026

Affected

2 pkgs

Patched

1 / 2

Exploits

None indexed

Blast Radius

2 pkgs affected

.NETDotNetNuke.Core.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

A module friendly name could include scripts that will run during some module operations in the Persona Bar.

Affected Packages

2 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`DotNetNuke.Core`	≥ 9.0.0	No fix
.NETNuGet	`DotNetNuke.Core`	≥ 10.0.0&&< 10.2.0	10.2.0

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
No patched version of DotNetNuke.Core has shipped for GHSA-vm5q-8qww-h238 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
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-vm5q-8qww-h238 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-vm5q-8qww-h238. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A module friendly name could include scripts that will run during some module operations in the Persona Bar.

O3 Security · Impact-Aware SCA

Is GHSA-vm5q-8qww-h238 in your dependencies?

O3 detects GHSA-vm5q-8qww-h238 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