CVE-2026-32730 | apostrophecms apostrophe up to 4.27.x Multi-Factor Authentication improper authentication

VDB-351634 · CVE-2026-32730 · GCVE-0-2026-32730 APOSTROPHECMS APOSTROPHE UP TO 4.27.X MULTI-FACTOR AUTHENTICATION IMPROPER AUTHENTICATION HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 6.7 $0-$5k 1.47+ Summaryinfo A vulnerability labeled as critical has been found in apostrophecms apostrophe up to 4.27.x. This affects an unknown function of the component Multi-Factor Authentication. Executing a manipulation can lead to improper authentication. The identification of this vulnerability is CVE-2026-32730. The attack may be launched remotely. There is no exploit available. The affected component should be upgraded. Detailsinfo A vulnerability has been found in apostrophecms apostrophe up to 4.27.x and classified as critical. This vulnerability affects an unknown part of the component Multi-Factor Authentication. The manipulation with an unknown input leads to a improper authentication vulnerability. The CWE definition for the vulnerability is CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes: ApostropheCMS is an open-source content management framework. Prior to version 4.28.0, the bearer token authentication middleware in `@apostrophecms/express/index.js` (lines 386-389) contains an incorrect MongoDB query that allows incomplete login tokens — where the password was verified but TOTP/MFA requirements were NOT — to be used as fully authenticated bearer tokens. This completely bypasses multi-factor authentication for any ApostropheCMS deployment using `@apostrophecms/login-totp` or any custom `afterPasswordVerified` login requirement. Version 4.28.0 fixes the issue. The advisory is available at github.com. This vulnerability was named CVE-2026-32730 since 03/13/2026. The exploitation appears to be difficult. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. The technical details are unknown and an exploit is not available. Upgrading to version 4.28.0 eliminates this vulnerability. Productinfo Vendor apostrophecms Name apostrophe Version 4.0 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 4.9 4.10 4.11 4.12 4.13 4.14 4.15 4.16 4.17 4.18 4.19 4.20 4.21 4.22 4.23 4.24 4.25 4.26 4.27 Website Product: https://github.com/apostrophecms/apostrophe/ CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 6.8 VulDB Meta Temp Score: 6.7 VulDB Base Score: 5.6 VulDB Temp Score: 5.4 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 8.1 CNA Vector (GitHub_M): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Improper authentication CWE: CWE-287 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: apostrophe 4.28.0 Timelineinfo 03/13/2026 CVE reserved 03/18/2026 +5 days VulDB entry created 03/19/2026 +0 days Advisory disclosed 03/19/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: github.com Status: Confirmed CVE: CVE-2026-32730 (🔒) GCVE (CVE): GCVE-0-2026-32730 GCVE (VulDB): GCVE-100-351634 Entryinfo Created: 03/19/2026 00:09 Changes: 03/19/2026 00:09 (64) Complete: 🔍 Cache ID: 99:7CC:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸