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.
Published: 2026-09-05
Score: 9.8 Critical
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The MStore API plugin for WordPress allows attackers to forge Firebase Phone Auth JWTs because the plugin does not validate the cryptographic signature of the token. By crafting a token signed with their own keys, an attacker can impersonate any phone number and gain access to existing WordPress accounts or create new accounts without any authentication.

Affected Systems

All installations of the inspireui MStore API plugin on WordPress with version 4.20.0 or earlier, which is the version range affected by this vulnerability.

Risk and Exploitability

This flaw carries a CVSS score of 9.8, indicating critical severity. No EPSS score is published, and the vulnerability is not listed in the CISA KEV catalog, yet the attack surface is wide: the issue is remotely exploitable via the plugin’s public API. An attacker can submit a forged token in a request that the plugin otherwise trusts, bypassing authentication checks entirely. Because no certificate validation is performed, the exploit requires only the ability to send an HTTP request to the vulnerable endpoint – no privileged access or internal network exposure is needed.

Generated by OpenCVE AI on September 5, 2026 at 06:23 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update the MStore API plugin to version 4.20.1 or later, which implements proper JWT signature verification in FirebasePhoneAuthHelper::verify_id_token().
  • If an update is not available, temporarily disable the Firebase Phone Auth feature or remove the plugin from the site to eliminate the vulnerable code path.
  • After applying the update or disabling the feature, enforce strict access controls on your WordPress REST API, ensuring that only authenticated users can call endpoints that consume Firebase authentication tokens.
  • Monitor your authentication logs for unusual token usage patterns and block or rate‑limit requests that include malformed or self‑signed JWTs.

Generated by OpenCVE AI on September 5, 2026 at 06:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 05 Sep 2026 05:45:00 +0000

Type Values Removed Values Added
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.
Title MStore API <= 4.20.0 - Unauthenticated Authentication Bypass via 'id_token' Parameter JWT Forgery
Weaknesses CWE-287
References
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: Wordfence

Published:

Updated: 2026-09-05T05:30:54.459Z

Reserved: 2026-06-26T16:43:47.206Z

Link: CVE-2026-13447

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-05T06:17:09.403

Modified: 2026-09-05T06:17:09.403

Link: CVE-2026-13447

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-05T06:30:04Z

Weaknesses