How severe is GHSA-9x4v-xfq5-m8x5?

No CVSS score has been assigned to GHSA-9x4v-xfq5-m8x5 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-9x4v-xfq5-m8x5?

GHSA-9x4v-xfq5-m8x5 affects the following packages: better-auth (npm). Ecosystems affected: npm.

How do I fix GHSA-9x4v-xfq5-m8x5?

Update better-auth to 1.1.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9x4v-xfq5-m8x5 is resolved across your whole dependency graph.

How do I detect GHSA-9x4v-xfq5-m8x5 in my npm dependencies?

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

How do I mitigate GHSA-9x4v-xfq5-m8x5 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-9x4v-xfq5-m8x5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-9x4v-xfq5-m8x5 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-9x4v-xfq5-m8x5?

GHSA-9x4v-xfq5-m8x5 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 54th 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-9x4v-xfq5-m8x5?

GHSA-9x4v-xfq5-m8x5 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-9x4v-xfq5-m8x5 published, and has it been updated?

GHSA-9x4v-xfq5-m8x5 was published on February 5, 2025 and was last updated on August 2, 2026. 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

Better Auth URL parameter HTML Injection (Reflected Cross-Site scripting)GHSA-9x4v-xfq5-m8x5

Fix: better-auth/better-auth@7ae340e

GHSA-9x4v-xfq5-m8x5 is a Cross-site Scripting (XSS) vulnerability in better-auth. A fix is available for better-auth — see the affected versions and patch details below.

Also known asCVE-2025-71404

Published

Feb 5, 2025

Updated

Aug 2, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-9x4v-xfq5-m8x5.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs54th percentile — riskier than 54% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg 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.

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

better-authnpm

18.7Mdownloads / week

Description

Summary

The better-auth /api/auth/error page was vulnerable to HTML injection, resulting in a reflected cross-site scripting (XSS) vulnerability.

Details

The value of error URL parameter was reflected as HTML on the error page: https://github.com/better-auth/better-auth/blob/05ada0b79dbcac93cc04ceb79b23ca598d07830c/packages/better-auth/src/api/routes/error.ts#L81

Impact

An attacker who exploited this vulnerability by coercing a user to visit a specially-crafted URL could execute arbitrary JavaScript in the context of the user's browser.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`better-auth`	≥ 0.0.2&&< 1.1.16	1.1.16`npm install better-auth@1.1.16`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for better-auth, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update better-auth to 1.1.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9x4v-xfq5-m8x5 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.

Frequently Asked Questions

### Summary The better-auth `/api/auth/error` page was vulnerable to HTML injection, resulting in a reflected cross-site scripting (XSS) vulnerability. ### Details The value of `error` URL parameter was reflected as HTML on the error page: https://github.com/better-auth/better-auth/blob/05ada0b79dbcac93cc04ceb79b23ca598d07830c/packages/better-auth/src/api/routes/error.ts#L81 ### Impact An attacker who exploited this vulnerability by coercing a user to visit a specially-crafted URL could execute arbitrary JavaScript in the context of the user's browser.

O3 Security · Impact-Aware SCA

Is GHSA-9x4v-xfq5-m8x5 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works