# CVE-2026-62236: grav-plugin-login < 3.8.11 CSRF via regenerate2FASecret

> Attackers can force logged-in Grav users to reset their 2FA secrets via CSRF, disrupting authentication and requiring re-enrollment.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **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:** 17 Jul 2026
- **Updated:** 17 Jul 2026
- **Also known as:** GHSA-f4c6-8fcq-j58x

## What is CVE-2026-62236?

CVE-2026-62236 is a low-severity vulnerability in getgrav grav, published on 17 Jul 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-plugin-login before 3.8.11 contains a cross-site request forgery (CSRF) vulnerability in the login.regenerate2FASecret frontend task, which regenerates and persists a new TOTP secret for the authenticated session user without any anti-CSRF nonce or Origin/Referer check. Because Grav core dispatches the task from the GET 'task:' URI parameter and the default session cookie is SameSite=Lax, an attacker can lure a logged-in victim to an off-site page that performs a top-level GET navigation, rotating the victim's TOTP secret so their enrolled authenticator no longer matches the server, effectively forcing 2FA re-enrollment. Sites configured with session.samesite: Strict are not affected.

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

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


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

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

## Is CVE-2026-62236 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-62236 is a low-severity vulnerability in getgrav grav, published on 17 Jul 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-62236 exists.

Affected product: getgrav grav. 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-62236/ (Markdown: https://insights.sbomify.com/CVE-2026-62236/index.md)
```

## Sources

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

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