How severe is GHSA-hrgx-7j6v-xj82?

GHSA-hrgx-7j6v-xj82 has a CVSS score of 7.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-hrgx-7j6v-xj82?

GHSA-hrgx-7j6v-xj82 affects the following packages: @keystone-6/auth (npm), @keystone-next/auth (npm). Ecosystems affected: npm.

How do I fix GHSA-hrgx-7j6v-xj82?

Update @keystone-6/auth to 1.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hrgx-7j6v-xj82 is resolved across your whole dependency graph.

How do I detect GHSA-hrgx-7j6v-xj82 in my npm dependencies?

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

How do I mitigate GHSA-hrgx-7j6v-xj82 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is GHSA-hrgx-7j6v-xj82 actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-hrgx-7j6v-xj82, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-hrgx-7j6v-xj82?

GHSA-hrgx-7j6v-xj82 has an EPSS (Exploit Prediction Scoring System) score of 2.8%, placing it in the 86th 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-hrgx-7j6v-xj82?

GHSA-hrgx-7j6v-xj82 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.

Is there exploit tooling available for GHSA-hrgx-7j6v-xj82?

A Nuclei detection template exists for GHSA-hrgx-7j6v-xj82, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-hrgx-7j6v-xj82 published, and has it been updated?

GHSA-hrgx-7j6v-xj82 was published on January 12, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

HIGH severity

Reflected cross-site scripting (XSS) vulnerabilityGHSA-hrgx-7j6v-xj82

HIGHFix: keystonejs/keystone@96bf833

GHSA-hrgx-7j6v-xj82 is a high-severity (CVSS 7.1) Cross-site Scripting (XSS) vulnerability in @keystone-6/auth. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for @keystone-6/auth — see the affected versions and patch details below.

Also known asCVE-2022-0087

Published

Jan 12, 2022

Updated

Nov 8, 2023

Affected

2 pkgs

Patched

1 / 2

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

2.8%probability of exploitation in next 30 days

Lower Risk+0.15%

Lower risk than most CVEs86th percentile — riskier than 86% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

4other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@keystone-6/authnpm

20Kdownloads / week

@keystone-next/authnpm

126downloads / week

Description

This security advisory relates to a capability for an attacker to exploit a reflected cross-site scripting vulnerability when using the @keystone-6/auth package.

Impact

The vulnerability can impact users of the administration user interface when following an untrusted link to the signin or init page. This is a targeted attack and may present itself in the form of phishing and or chained in conjunction with some other vulnerability.

Vulnerability mitigation

Please upgrade to @keystone-6/auth >= 1.0.2, where this vulnerability has been closed. If you are using @keystone-next/auth, we strongly recommend you upgrade to @keystone-6.

Workarounds

If for some reason you cannot upgrade the dependencies in software, you could alternatively

disable the administration user interface, or
if using a reverse-proxy, strip query parameters when accessing the administration interface

References

https://owasp.org/www-community/attacks/xss/

Thanks to Shivansh Khari (@Shivansh-Khari) for discovering and reporting this vulnerability

Affected Packages

2 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@keystone-6/auth`	all versions	1.0.2`npm install @keystone-6/auth@1.0.2`
📦npm	`@keystone-next/auth`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

keystonekeystonejs

< 1.0.2

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

keystone is vulnerable to Improper Neutralization of Input During Web Pa…

huntr.devNVDJan 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @keystone-6/auth, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @keystone-6/auth to 1.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hrgx-7j6v-xj82 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

How to detect GHSA-hrgx-7j6v-xj82

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id ghsa-hrgx-7j6v-xj82 -u https://target

Template: Keystone 6 Login Page - Open Redirect and Cross-Site Scripting
Severity: medium
Impact: Attackers can redirect users to malicious websites or inject malicious JavaScript via the from parameter, potentially facilitating phishing attacks or stealing user credentials.
Remediation: Please upgrade to @keystone-6/auth >= 1.0.2, where this vulnerability has been closed. If you are using @keystone-next/auth, we strongly recommend you upgrade to @keystone-6

Template by ProjectDiscovery nuclei-templates (ShivanshKhari), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

This security advisory relates to a capability for an attacker to exploit a reflected cross-site scripting vulnerability when using the `@keystone-6/auth` package. #### Impact The vulnerability can impact users of the administration user interface when following an untrusted link to the `signin` or `init` page. This is a targeted attack and may present itself in the form of phishing and or chained in conjunction with some other vulnerability. ## Vulnerability mitigation Please upgrade to `@keystone-6/auth >= 1.0.2`, where this vulnerability has been closed. If you are using `@keystone-next/a