CVE-2026-130677 json
Craft CMS 5.0.0 before 5.11.4 2FA Session Invalidation and Re-authentication Bypass
published 15d ago modified 53m ago also GHSA-j2r3-x468-c6j5
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository craftcms/cms. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 8.7
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
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.
Patch / fix
- packagist craftcms/cms 5.11.4
- craftcms cms 5.11.4
Is CVE-2026-130677 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 8.7 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | craftcms/cms | >=5.0.0, <5.11.4 |
5.11.4 |
Affected products
- craftcms cms
Classification
- Weakness
-
- CWE-272 Least Privilege Violation
- Technology feeds
References
-
github.com
/craftcms/cms/security/advisories/GHSA-j2r3-x468-c6j5
vendor-advisory, advisory
Sources
- CVE List CVE-2026-130677
- NVD CVE-2026-130677
- Maintainer advisory GHSA-j2r3-x468-c6j5
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of craftcms/cms published their own advisory on GitHub. Reviewed sources take precedence over it.