Authentication Bypass in Mstore Api Plugin for WordPress via JWT Forgery
The Mstore Api plugin for WordPress (<= 4.20.0) is vulnerable to authentication bypass via JWT forgery, allowing unauthenticated attackers to impersonate any user by crafting illegitimate Firebase Phone Auth tokens.
CVE search metadata
CVE search record: CVE-2026-13447. Severity: critical. CVSS: 9.8. KEV: no. Product: Mstore Api (<= 4.20.0). Brief: Authentication Bypass in Mstore Api Plugin for WordPress via JWT Forgery. Brief link: https://feed.craftedsignal.io/briefs/2026-09-mstore-api-auth-bypass/
The Mstore Api plugin for WordPress is susceptible to an authentication bypass vulnerability, tracked as CVE-2026-13447, affecting all versions up to and including 4.20.0. The vulnerability resides in the FirebasePhoneAuthHelper::verify_id_token() function, which is responsible for validating Firebase identity tokens. The implementation properly decodes JWT claims such as 'alg', 'kid', 'aud', and 'iss', but completely fails to perform cryptographic signature verification. Specifically, the function neglects to call openssl_verify() or utilize any mechanism to validate the token against Google's public key infrastructure. Consequently, an unauthenticated attacker can supply a forged JWT signed with a custom RSA key pair, effectively bypassing authentication checks. This allows for unauthorized access to existing WordPress user accounts associated with specific phone numbers or the creation of new, arbitrary accounts with elevated privileges.
Attack Chain
- Attacker identifies a WordPress site utilizing the Mstore Api plugin version 4.20.0 or earlier.
- Attacker interacts with the plugin authentication endpoint that triggers the FirebasePhoneAuthHelper::verify_id_token() function.
- Attacker generates a custom RSA key pair to sign a malicious JWT.
- Attacker constructs a forged JWT with claims matching the target user or arbitrary account details.
- Attacker transmits the forged JWT to the vulnerable plugin endpoint.
- The plugin logic decodes the provided JWT and validates claims, but skips signature verification, accepting the forged token as valid.
- The plugin grants the attacker an authenticated session context for the impersonated identity.
- Attacker gains unauthorized access to the victim's account data or account creation functionality.
Impact
Successful exploitation enables unauthenticated remote attackers to bypass identity verification, leading to account takeover or the unauthorized creation of arbitrary user accounts. This grants attackers access to sensitive user data and administrative functions within the WordPress environment. The 9.8 CVSS score reflects the high potential for full compromise of user accounts and the relative ease of generating forged tokens due to the total absence of cryptographic validation.
Recommendation
- Immediately update the Mstore Api plugin to the latest available version beyond 4.20.0 to remediate CVE-2026-13447.
- Audit access logs for suspicious account authentication patterns or unexpected account creations tied to phone-based registration workflows.
- If the latest patch cannot be applied, disable the plugin to eliminate the vulnerable endpoint from the attack surface.
Immediate actions
Upgrade Mstore Api plugin to a version patched against CVE-2026-13447
Mitigations
Disable Mstore Api plugin if patching is not immediately feasible
CVE-2026-13447