CVE-2026-61451: Grav before 1.0.4 Password Reset Token Poisoning via admin_base_url
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.
Security readout for executives and security teams
Plain-English summary
This flaw lets an unauthenticated attacker influence where a password reset link points. If a user clicks the poisoned reset email, the valid reset token can be exposed to the attacker, enabling account takeover. The impact is severe, but the supplied sources do not show known active exploitation.
Executive priority
Treat as urgent for exposed Grav systems because successful abuse can lead to administrator account takeover. Prioritize patching public sites and any deployment where password reset is enabled.
Technical view
Grav API plugin before 1.0.4 accepts a client-controlled admin_base_url in the forgot-password flow and only validates the URL scheme. It does not verify the host against the server origin. Referer or Origin headers may also influence the base URL, causing reset emails to include attacker-controlled links.
Likely exposure
Internet-facing Grav sites using the vulnerable Grav API plugin password-reset endpoint are the main concern. Exposure depends on whether grav-plugin-api before 1.0.4 is installed and the forgot-password route is reachable.
Exploitation context
The source bundle describes network exploitation without authentication, low complexity, and required user interaction. Account takeover occurs only if the victim follows the poisoned reset link. KEV status is false, and no cited source confirms active exploitation.
Researcher notes
Evidence supports improper URL origin validation in the reset workflow, mapped to CWE-601. The affected version boundary is stated as before 1.0.4. Do not assume exploitation in the wild without new KEV or advisory evidence.
Mitigation direction
Upgrade grav-plugin-api to version 1.0.4 or later.
Review the GitHub advisory for vendor-specific guidance.
Restrict or monitor access to the forgot-password API endpoint until upgraded.
Review recent password reset activity for suspicious hosts or unexpected reset flows.
Validation and detection
Inventory Grav deployments and confirm grav-plugin-api versions.
Check whether POST /api/v1/auth/forgot-password is reachable externally.
Verify reset emails use the legitimate site origin only.
Review logs for unusual Origin, Referer, or admin_base_url values.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-601: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.