External risk intelligence

Mstore Api WordPress Plugin JWT Forgery Authentication Bypass

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-13447

The vulnerability exists in a WordPress plugin that provides API functionality. Such plugins are commonly deployed to facilitate public-facing web and mobile application interactions, making the authentication endpoints they expose reachable via the public internet as part of standard site operations.

Authentication Bypass

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This critical vulnerability affects the Mstore Api plugin for WordPress, allowing unauthenticated attackers to bypass authentication and gain unauthorized access to user accounts. The flaw stems from a failure to properly verify digital signatures on authentication tokens, enabling the forgery of credentials. This could lead to account takeovers or the creation of fraudulent accounts within affected WordPress sites.

  • Plugin allows unauthorized account access.
  • Bypasses security by forging authentication tokens.
  • Confirm relevance and check for exposure.

Attack Path

How an attacker could exploit the issue

An attacker can forge a Firebase Phone Auth JSON Web Token (JWT) because the Mstore Api plugin for WordPress fails to properly verify its signature. This allows an unauthenticated attacker to impersonate any phone number, leading to unauthorized access to existing accounts or the creation of new ones.

  • No authentication required to initiate attack.
  • Forging a JWT to bypass authentication.
  • Unauthorized account access or creation.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow unauthenticated attackers to bypass authentication and impersonate any user, potentially leading to unauthorized access or account creation. The issue stems from a missing signature verification for Firebase ID tokens within the Mstore Api plugin for WordPress.

  • WordPress account access.
  • Forging authentication tokens.
  • Unauthorized account access or creation.

Operational Fix

Recommended remediation, mitigation, and detection steps

Infrastructure, platform, and security teams are likely responsible for addressing this critical vulnerability in the Mstore Api plugin for WordPress. The first practical step is to identify all WordPress instances utilizing this plugin, confirm their exposure and business criticality, and then assign an accountable owner to plan remediation.

  • Infrastructure and platform teams own remediation.
  • Verify plugin reachability and business criticality.
  • Plan updates or vendor coordination.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the Mstore Api plugin?

The Mstore Api is a WordPress plugin designed to bridge the gap between WordPress websites and mobile applications, often facilitating Flutter-based commerce experiences. It provides the necessary backend endpoints to handle user interactions, such as logging in via phone numbers using services like Firebase, allowing the site to function as a data source for external mobile apps.

How does CVE-2026-13447 create an authentication bypass?

This vulnerability, classified as Improper Authentication (CWE-287), occurs because the plugin fails to perform cryptographic signature verification on JSON Web Tokens (JWTs). While the code checks the token's structural claims, it skips the essential step of verifying the token's authenticity against official public keys. This allows an attacker to create their own forged token that the plugin mistakenly accepts as legitimate.

What must happen for an attacker to trigger this flaw?

An attacker must generate a fraudulent JWT signed with their own RSA key pair and submit it to the vulnerable authentication endpoint. Simply visiting the site or interacting with standard WordPress login forms does not trigger the bug. The attack requires active interaction with the specific API functions that process Firebase Phone Auth tokens without proper signature validation.

Why is this plugin considered a relevant security concern?

Halo Surface Signal notes that since this plugin powers API functionality for mobile and web apps, its endpoints are typically reachable over the public internet to support normal site operations. Because the plugin is exposed to these network interactions, the authentication bypass can be attempted remotely by anyone with access to the site's public API, making it a high-priority risk.

How should I respond if I use this plugin?

Your first step is to locate all WordPress instances in your environment that have the Mstore Api plugin installed. Once identified, evaluate the business criticality of those sites and determine if they rely on the affected Firebase authentication features. Coordinate with your technical team to track vendor updates or disable the plugin until a secure, patched version is confirmed and applied.

References