How severe is GHSA-xr8f-59pp-rxxh?

No CVSS score has been assigned to GHSA-xr8f-59pp-rxxh yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-xr8f-59pp-rxxh?

GHSA-xr8f-59pp-rxxh affects the following packages: Microsoft.AspNetCore.SpaServices (NuGet), Microsoft.AspNetCore.SpaServices (NuGet). Ecosystems affected: NuGet.

How do I fix GHSA-xr8f-59pp-rxxh?

Update Microsoft.AspNetCore.SpaServices to 2.2.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xr8f-59pp-rxxh is resolved across your whole dependency graph.

How do I detect GHSA-xr8f-59pp-rxxh in my NuGet dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Microsoft.AspNetCore.SpaServices, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-xr8f-59pp-rxxh 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.

Is GHSA-xr8f-59pp-rxxh actively exploited in the wild?

No public exploit code has been indexed for GHSA-xr8f-59pp-rxxh 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-xr8f-59pp-rxxh?

GHSA-xr8f-59pp-rxxh has an EPSS (Exploit Prediction Scoring System) score of 4.8%, placing it in the 92th 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-xr8f-59pp-rxxh?

GHSA-xr8f-59pp-rxxh is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-xr8f-59pp-rxxh published, and has it been updated?

GHSA-xr8f-59pp-rxxh was published on May 24, 2022 and was last updated on December 3, 2024. 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

Not in CISA KEV

Elevation of privilege in ASP.NET CoreGHSA-xr8f-59pp-rxxh

GHSA-xr8f-59pp-rxxh is a Improper Input Validation vulnerability in Microsoft.AspNetCore.SpaServices. A fix is available for Microsoft.AspNetCore.SpaServices — see the affected versions and patch details below.

Also known asCVE-2019-1302

Published

May 24, 2022

Updated

Dec 3, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

4.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs92th percentile — riskier than 92% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

.NETMicrosoft.AspNetCore.SpaServices.NETMicrosoft.AspNetCore.SpaServices

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

An elevation of privilege vulnerability exists when a ASP.NET Core web application, created using vulnerable project templates, fails to properly sanitize web requests, aka 'ASP.NET Core Elevation Of Privilege Vulnerability'.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`Microsoft.AspNetCore.SpaServices`	≥ 2.2.0&&< 2.2.7	2.2.7`dotnet add package Microsoft.AspNetCore.SpaServices --version 2.2.7`
.NETNuGet	`Microsoft.AspNetCore.SpaServices`	≥ 2.1.0&&< 2.1.13	2.1.13`dotnet add package Microsoft.AspNetCore.SpaServices --version 2.1.13`

Affected Products

1 product · 3 configurations

Application

asp.net coremicrosoft

3 versions

2.12.23.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Microsoft.AspNetCore.SpaServices, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update Microsoft.AspNetCore.SpaServices to 2.2.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xr8f-59pp-rxxh 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.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-xr8f-59pp-rxxh in your dependencies?

Find it across NuGet, including transitive dependencies.

Scan my dependencies How O3 SCA works