CVE-2026-55186: MultiFactor Authentication for SilverStripe can bypass MFA during password reset flow
In the SilverStripe `silverstripe/mfa` module on CMS 5, the password reset flow let a user with multi-factor authentication enabled set a new password and get a logged-in session without completing MFA. The attacker needs access to the victim's email account. Version 6.0.0 fixes it, and CMS 6 is not affected.
Published Oct 29, 2026 · Updated Nov 3, 2026 · Analysis Oct 31, 2026
What an attacker can do
Password reset links normally prove control of the user's email. In the affected flow, completing the reset also logged the user in, and that login skipped the MFA step. MFA exists to protect an account when the password or the email is compromised, so this removes that second layer for the reset path (CWE-288, authentication bypass using an alternate path).
The attacker must already read the victim's mailbox, to receive the reset link, and must know the account to target. They also need a low-privilege starting point per the CVSS vector, and the attack complexity is rated high. With those in hand they request a reset, follow the emailed link, choose a password and land in a logged-in session as the victim, including administrators of the CMS.
The impact is limited because email access is a strong precondition. Sites that rely on MFA as the control against mailbox compromise are the ones that lose the protection.
Who is affected
The Composer package silverstripe/mfa below 6.0.0 is affected, on SilverStripe CMS 5 sites where users have MFA enabled. CMS 6 is not affected. Check the installed version:
composer show silverstripe/mfaIf the command shows a 4.x or 5.x release on a CMS 5 site, treat the site as exposed.
silverstripe/mfa
- Ecosystem
- Composer (PHP)
- Affected
- < 6.0.0
- Fixed in
- 6.0.0
- Check
composer show silverstripe/mfa
How to fix it
The data lists 6.0.0 as the patched version of silverstripe/mfa.
composer require silverstripe/mfa:^6.0For a CMS 5 site, check the SilverStripe security release notice for the fixed release that matches your CMS line before upgrading, since module 6.0.0 may require CMS 6. The advisory gives no workaround.
How to tell if you were hit
Review login and password reset activity for MFA-enabled accounts: a successful login directly after a password reset, with no MFA challenge recorded, is the pattern. Check for reset emails the account owner did not request, and for password changes you cannot explain.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
Impact
In CMS 5, the password reset flow let a user with multi-factor authentication enabled change their password and get a logged-in session before completing multi-factor authentication. Exploiting this requires access to the user's email account. CMS 6 is not affected.
Questions
- Does the attacker need the victim's password?
No. They need access to the victim's email account to use the reset link, then set a new password themselves.
- Is SilverStripe CMS 6 affected?
No. The advisory says CMS 6 is not affected; the issue is in the CMS 5 password reset flow.
- Is CVE-2026-55186 exploited in the wild?
No source reports exploitation, and it is not in CISA's KEV catalog.
References
Read for this analysis:
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
