Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2025-71404

Cross-Site Scripting (XSS) in better-auth (CVE-2025-71404)

Summary

Cross-site scripting in better-auth (CVE-2025-71404). Risk of unauthorized operations or information disclosure. Exploitable via error. Mitigation: upgrade to 1.1.16 or later.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2025-71404 has been found in better-auth.
Attackers can target a specific entry point like error over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade better-auth to 1.1.16 or later.
If unsure, ask your IT team or search "better-auth CVE-2025-71404" on the vendor's site.

CVE-2025-71404 (better-auth) — CWE-79
Attack surface: error
Patched: 1.1.16 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Cross-site scripting (XSS) (CWE-79) exists in better-auth. Attackers reach the vulnerable code path via error.

📍 Affected scope

Check the vendor advisory for the affected versions of better-auth. Attack surface: error.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.1.16.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'better-auth' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'better-auth' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で better-auth を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade better-auth to 1.1.16

    ステージング環境で 1.1.16 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm better-auth
[{"type":"SEMVER","events":[{"introduced":"0.0.2"},{"fixed":"1.1.16"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details