CVE-2026-32730
Authentication Bypass in ApostropheCMS via Incomplete MFA Verification
Publication date: 2026-03-18
Last updated on: 2026-03-24
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| apostrophecms | apostrophecms | to 4.28.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-287 | When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. |
| CWE-305 | The authentication algorithm is sound, but the implemented mechanism can be bypassed as the result of a separate weakness that is primary to the authentication error. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in ApostropheCMS versions prior to 4.28.0 in the bearer token authentication middleware located in `@apostrophecms/express/index.js`. The issue is caused by an incorrect MongoDB query that allows incomplete login tokens—where the password has been verified but the Time-based One-Time Password (TOTP) or Multi-Factor Authentication (MFA) requirements have not been fulfilled—to be accepted as fully authenticated bearer tokens.
As a result, this flaw completely bypasses multi-factor authentication for any ApostropheCMS deployment that uses `@apostrophecms/login-totp` or any custom login requirement that runs after password verification. The vulnerability was fixed in version 4.28.0.
How can this vulnerability impact me? :
This vulnerability can have a severe impact because it allows attackers to bypass multi-factor authentication controls. An attacker who has obtained a valid password can use an incomplete login token to gain full authenticated access without completing the second factor of authentication.
This leads to a high risk of unauthorized access, potentially compromising the confidentiality, integrity, and availability of the ApostropheCMS deployment and its data.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade ApostropheCMS to version 4.28.0 or later, where the issue with bearer token authentication middleware has been fixed.
Ensure that any deployment using `@apostrophecms/login-totp` or custom `afterPasswordVerified` login requirements is updated to prevent bypassing multi-factor authentication.