Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-62232 – Two-Factor Authentication Bypass in Grav CMS (before 2.0.4)

Be the first to know when new zero-days emerge:

Summary

CVE-2026-62232 is a critical two-factor authentication (2FA) bypass vulnerability in Grav CMS’s login plugin, affecting all versions prior to 2.0.4. The flaw stems from a missing authorization check in the taskRegenerate2FASecret function, allowing a network-based attacker who possesses a victim’s password to silently overwrite the victim’s TOTP secret and complete 2FA authentication without ever possessing the original second factor. With a CVSS v4.0 score of 9.1 (Critical) and a CVSS v3.1 score of 7.4 (High), this vulnerability effectively reduces 2FA-protected Grav accounts to password-only protection.

Technical details

  • Root cause: Three compounding security failures exist in user/plugins/login/classes/Controller.php: (1) the login plugin assigns $session->user = $user before TOTP verification completes, leaving the user object accessible during the pending-challenge state; (2) the taskRegenerate2FASecret function checks only whether the user exists (exists()), not whether the user is authorized (authorized()); and (3) the regenerate 2FA secret endpoint performs no CSRF nonce validation.
  • Trigger conditions: An attacker must know the victim’s account password. Exploitation occurs during the TOTP pending-challenge window that opens after a correct password is submitted.
  • Attack vector: Network-accessible; no privileges on the target system are required. The attacker sends a crafted unauthenticated HTTP request to the regenerate2FASecret task endpoint, receives the newly generated TOTP secret in the plaintext JSON response, computes a valid TOTP code from that attacker-chosen secret, and then completes authentication as the victim.
  • Impact: Full account takeover with high confidentiality and integrity impact (VC:H/VI:H). The victim’s original 2FA secret is permanently overwritten, which can also result in the victim being locked out of their own account.

Affected software

  • Grav CMS — all versions before 2.0.4 (inclusive of 2.0.3 and earlier)

Severity

  • CVSS v4.0: 9.1 (Critical) — CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
  • CVSS v3.1: 7.4 (High) — CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
  • CWE: CWE-862 (Missing Authorization)

Mitigation and recommended actions

  • Immediate — upgrade: Update Grav to version 2.0.4 or later. The fix is available in the official Grav releases; version 2.0.11 is the current latest release as of this advisory.
  • If immediate patching is not feasible: Restrict network access to the Grav admin and login endpoints at the web server or perimeter firewall level to trusted IP ranges only, reducing the attacker’s ability to reach the vulnerable endpoint.
  • Operational: Review Grav admin account activity logs for any unexpected session activity or 2FA secret changes in the period prior to patching, as exploitation leaves no inherent user-visible indicator.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge