CVE-2026-18233

MStore API – Create Native Android & iOS Apps On The Cloud < 4.21.1 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Order Completion

2026-08-27 00:00
Erwan LR

Strategic Overview

Status
Patched in 4.21.1
Affected Plugin
MStore API – Create Native Android & iOS Apps On The Cloud
Affected Version
< 4.21.1
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-18233
View all MStore API – Create Native Android & iOS Apps On The Cloud vulnerabilities

At a glance

CVE-2026-18233 is a medium-severity Missing Authorization vulnerability in the MStore API WordPress plugin, affecting versions < 4.21.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 4.21.1; sites on affected versions should update now. Disclosed August 2026, reported by Erwan LR.

Vulnerability Overview

The MStore API – Create Native Android & iOS Apps On The Cloud plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on a function in all versions up to 4.21.1 (exclusive). This makes it possible for authenticated attackers, with Subscriber-level access and above, to mark orders as completed.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in MStore API < 4.21.1 takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For MStore API the fix is 4.21.1: builds < 4.21.1 are affected, anything from 4.21.1 onward is not.

Remediation

Update to version 4.21.1, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: MStore API 4.21.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-18233https://www.wordfence.com/threat-intel/vulnerabilities/id/597dc29a-3a5c-412c-849b-9c5640181d0chttps://nvd.nist.gov/vuln/detail/CVE-2026-18233

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C