Skip to main content
Menu
CVEs

CVE

Craftcms CMS auth bypass in 2FA session management

Affects Craft CMS 5.0.0 before 5.11.4 on accounts with 2FA enabled or being set up, where a session on another device or browser stays valid after 2FA is enabled. Fixed in 5.11.4.

CVE-2026-130677Published Updated Summary written by a model

8.7HighCNA
Exploited
No known exploitation
Fix
Fixed in 5.11.4
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 5.11.4.

Summary

Craft CMS from 5.0.0 before 5.11.4 contains an improper session management vulnerability that fails to invalidate existing sessions when 2FA is enabled and allows disabling 2FA without re-authentication. Attackers holding a hijacked or stale session can retain full account access and silently remove 2FA without the password, authenticator code, or recovery code.

Who should check

Teams running Craft CMS 5.0.0 through 5.11.3 with 2FA enabled on user accounts, especially sites where admins sign in from shared computers.

“Affected versions >= 5.0.0, < 5.11.4”

github.com

cve.now Index

29Pcve.now Index 29 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.7/10CVSS 8.7
  • No patch0/5No signal

What would change the score

  • Would score about 74 if added to CISA KEV
  • Would score about 69 if CISA's SSVC rates exploitation active
  • Would score about 34 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 5.11.4.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-130677 (Craft CMS 5.0.0 before 5.11.4 2FA Session Invalidation and Re-authentication Bypass), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130677 (entry last updated 2026-11-18):
Affected:
- craftcms cms: from 5.0.0, fixed in 5.11.4
Fixed versions: 5.11.4.
Conditions (all must be true for the bug to be hit):
- Account has 2FA enabled or is being set up with 2FA (source: https://github.com/craftcms/cms/security/advisories/GHSA-j2r3-x468-c6j5)
- An existing session on another device or browser remains valid after 2FA is enabled (source: https://github.com/craftcms/cms/security/advisories/GHSA-j2r3-x468-c6j5)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-130677 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130677 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/craftcms/cms/security/advisories/GHSA-j2r3-x468-c6j5
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130677
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130677"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Affected versions

  • craftcms cms

    From 5.0.0 · fixed in 5.11.4

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · craftcms/cms · Advisory GHSA-j2r3-x468-c6j5
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-130677
RecordNVD · CVE-2026-130677

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130677

Is CVE-2026-130677 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

After 2FA is turned on, a session that already exists on another device or browser is not invalidated. Someone holding that active or hijacked session can turn off 2FA without the password, a 2FA code, or a recovery code, and keep full account access.Source: github.com

Which versions are affected by CVE-2026-130677?

cms: from 5.0.0 before 5.11.4.Source: cve.now feed data

Am I affected, and how do I check?

Craft CMS versions from 5.0.0 up to but not including 5.11.4, on accounts that have 2FA enabled or are being set up with 2FA. To check, look at the installed Craft CMS version and whether the account has 2FA enabled under Security settings.Source: github.com

How do I fix CVE-2026-130677?

Upgrade Craft CMS to 5.11.4 or later, the version that fixes this issue.Source: github.com

More CVEs