CVE-2026-18234

MStore API – Create Native Android & iOS Apps On The Cloud < 4.21.1 - Missing Authorization

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
6.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-18234
View all MStore API – Create Native Android & iOS Apps On The Cloud vulnerabilities

At a glance

CVE-2026-18234 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the MStore API WordPress plugin, affecting versions < 4.21.1. It carries a CVSS score of 6.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. 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 perform an unauthorized action.

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-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in MStore API < 4.21.1 takes a caller who can reach the endpoint. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. 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-18234https://www.wordfence.com/threat-intel/vulnerabilities/id/ee49e76a-fc6f-4c23-ac44-29625b1d5000https://nvd.nist.gov/vuln/detail/CVE-2026-18234

Related records

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