# CVE-2026-62671: Cross-site request forgery in grav-plugin-login

> An anonymous attacker can force a logged-in user to reset their 2FA secret via CSRF, bypassing two-factor authentication protections.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Aug 2026
- **Updated:** 19 Aug 2026
- **Also known as:** GHSA-4px8-7p53-282r

## What is CVE-2026-62671?

CVE-2026-62671 is a medium-severity vulnerability in getgrav grav-plugin-login, published on 19 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Grav Login Plugin adds login, basic ACL, and session wide messages to Grav. Prior to 3.8.11, the Grav Login plugin login.regenerate2FASecret task accepts a top-level GET request through the TaskServiceProvider task: URI parameter without requiring a login-form nonce, an Origin check, or a Referer check. Under the default SameSite=Lax session cookie policy, an off-site navigation can invoke taskRegenerate2FASecret() in a logged-in victim's session, overwrite the victim's TOTP secret, and force two-factor re-enrollment. This issue is fixed in version 3.8.11.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2026-62671?


## How do I fix CVE-2026-62671?

No fix has been published for CVE-2026-62671 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-62671 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62671 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-62671 and fix it if it is affected.

What it is: CVE-2026-62671 is a medium-severity vulnerability in getgrav grav-plugin-login, published on 19 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62671 exists.

Affected product: getgrav grav-plugin-login. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-62671/ (Markdown: https://insights.sbomify.com/CVE-2026-62671/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-62671
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-62671
- OSV: https://osv.dev/vulnerability/CVE-2026-62671

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-62671/
Summaries are generated and may contain mistakes; the official description above is the record.