Description
The Mstore Api plugin for WordPress is vulnerable to Authentication Bypass via JWT Forgery in versions up to, and including, 4.20.0 This is due to missing cryptographic signature verification in the FirebasePhoneAuthHelper::verify_id_token() function, which decodes and validates Firebase ID token claims (alg, kid, aud, iss) but never calls openssl_verify() or any equivalent to validate the JWT signature against Google's actual public key certificates. This makes it possible for unauthenticated attackers to forge a Firebase Phone Auth JWT signed with a self-generated RSA key pair and impersonate any phone number, resulting in unauthorized access to existing WordPress accounts or creation of new arbitrary accounts.
References7
- plugins.trac.wordpress.org/browser/mstore-api/tags/4.18.4/contr…
- plugins.trac.wordpress.org/browser/mstore-api/tags/4.18.4/contr…
- plugins.trac.wordpress.org/browser/mstore-api/tags/4.18.4/contr…
- plugins.trac.wordpress.org/browser/mstore-api/trunk/controllers…
- plugins.trac.wordpress.org/browser/mstore-api/trunk/controllers…
- plugins.trac.wordpress.org/browser/mstore-api/trunk/controllers…
- www.wordfence.com/threat-intel/vulnerabilities/id/4a1127af-74f6…
Metrics
- CVSS 3.1
-
9.8
CRITICAL
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - EPSS — exploit probability
- 1% percentile: 53 · as of 7 November 2026
- CWE
- CWE-287
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.