Open Redirect in Grav API plugin (CVE-2026-61451)
Summary
Vulnerability in Grav API plugin (CVE-2026-61451). Successful exploitation can lead to full system takeover. Exploitable via POST /api/v1/auth/forgot-password.
Original description
The description as published by the source.
The Grav API plugin (grav-plugin-api) before 1.0.4 does not validate the origin of the client-supplied admin_base_url field in the POST /api/v1/auth/forgot-password endpoint. The sanitizeHttpUrl() function only checks that the URL scheme is http/https and never verifies the host against the server's own origin, so an attacker can supply an arbitrary host. As a result, an unauthenticated attacker can cause the password reset email sent to a victim to contain a reset link pointing at an attacker-controlled server; when the victim follows the link, the valid reset token is disclosed to the attacker, enabling full account takeover. The vulnerable base URL can also be influenced via the Referer or Origin headers.
Source: GitHub Security Advisories (Global) 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-2026-61451 has been found in Grav API plugin.
Attackers can target a specific entry point like POST /api/v1/auth/forgot-password over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.6/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Grav API plugin CVE-2026-61451" on the vendor's site.
CVE-2026-61451 (Grav API plugin) — CWE-601 / CVSS v3 9.6
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: POST /api/v1/auth/forgot-password
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.
A vulnerability (CWE-601) exists in Grav API plugin. Attackers reach the vulnerable code path via POST /api/v1/auth/forgot-password without authentication.
Check the vendor advisory for the affected versions of Grav API plugin. Attack surface: POST /api/v1/auth/forgot-password.
Severity: Critical (CVSS 9.6/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /api/v1/auth/forgot-password requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Grav API plugin を使っているサービスとバージョンを洗い出す。
-
2Hunt for indicators of compromise detect
grep 'POST /api/v1/auth/forgot-password' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/v1/auth/forgot-passwordへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against POST /api/v1/auth/forgot-password on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- web github.com
- web nvd.nist.gov
- web disclosure@vulncheck.com
- web github.com