External risk intelligence

MStore API WordPress Plugin Order Paid Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-16038

The vulnerability exists in a WordPress plugin within payment-completion endpoints. Because these endpoints are designed to receive external callbacks from payment gateways and process orders from public-facing e-commerce storefronts, they are inherently and intentionally exposed to the public internet by design.

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

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability has been identified in the MStore API WordPress plugin. This issue allows attackers to bypass payment gateways, enabling them to obtain goods or services without payment. The primary concern is to confirm if this plugin is in use and if it has been exposed to potential exploitation.

  • Attackers can get free products by skipping payments.
  • Confirms basic security for e-commerce operations.
  • Ensure payment integrity and prevent unauthorized access.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by sending a request to the MStore API's payment-completion endpoints. Because the API does not properly verify payments with the payment gateway, the attacker can trick the system into marking any order as fully paid without making an actual payment. This could lead to the attacker obtaining goods or services for free.

  • Unauthenticated access to API endpoints.
  • Bypassing payment verification.
  • Free goods or services.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability in the MStore API WordPress plugin could allow an unauthenticated attacker to bypass payment processing and obtain goods or services without payment. This could impact the integrity of sales transactions and result in financial loss for the site owner.

  • Order fulfillment data at risk.
  • Unauthenticated requests bypass payment.
  • Loss of revenue and goods.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in the MStore API WordPress plugin affects order fulfillment, making it critical for e-commerce operations. The primary responsibility likely falls to the Application Owners or the Platform Team managing the WordPress instance, with support from the Security Team for exposure assessment and Vendor Management for plugin updates. The immediate first step is to identify all instances of the plugin, confirm their exposure and criticality, and then coordinate remediation based on business impact and available maintenance windows.

  • Application or Platform team ownership.
  • Verify plugin usage and exposure.
  • Plan remediation during maintenance.

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 WordPress plugin?

MStore API is a plugin used within the WordPress ecosystem to power mobile shopping experiences. It acts as a bridge, allowing e-commerce storefronts to connect with mobile applications so that users can browse products and place orders directly from their devices.

How does CVE-2026-16038 create a security risk?

This vulnerability is classified as Improper Authorization (CWE-862). It occurs because the plugin fails to check if a payment actually succeeded before finalizing an order. By exploiting this logic flaw, an unauthorized person can send a crafted request to the system, forcing it to treat an unpaid order as fully paid.

Do I need to be logged in to trigger this vulnerability?

No. The issue exists in the plugin's payment-completion endpoints, which are designed to accept data from external services. Because these endpoints do not require user authentication, anyone on the internet can send a request to them. Normal site browsing or standard administrative actions are not what triggers this; it requires specific, malicious requests sent to those payment endpoints.

Is my site relevant to this MStore API threat?

If you run a WordPress store using this plugin, your site is likely relevant. Halo Surface Signal notes that because the affected payment-completion endpoints must communicate with public-facing payment gateways, they are inherently reachable from the internet. This design means the risk applies to any site actively using the vulnerable version, regardless of internal firewall configurations.

When should I update my MStore API plugin?

You should prioritize updating immediately to version 4.21.0 or later. Your first step is to confirm whether this plugin is active on your WordPress instance. Once identified, coordinate with your team to apply the update through your standard maintenance process to close the payment verification gap and protect your transaction integrity.

References