CVE-2023-3131

MStore API <= 3.9.6 - Missing Authorization

2023-06-12 00:00
Truoc Phan

Strategic Overview

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

At a glance

CVE-2023-3131 is a medium-severity Missing Authorization vulnerability in the MStore API WordPress plugin, affecting versions < 3.9.7. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.9.7; sites on affected versions should update now. Disclosed June 2023, reported by Truoc Phan.

Vulnerability Overview

The MStore API plugin for WordPress is vulnerable to unauthorized modification of data due to missing capability checks on several functions called via AJAX actions such as mstore_delete_json_file, mstore_update_limit_product, mstore_update_firebase_server_key, mstore_update_new_order_title, mstore_update_new_order_message, mstore_update_status_order_title, and mstore_update_status_order_message in versions up to, and including, 3.9.6. This makes it possible for authenticated attackers with minimal permissions, such as a subscriber, to perform several unauthorized actions that allow the attacker to control the plugins settings. This was partially patched in 3.9.6 but not fully patched until 3.9.7. CVE-2023-3209 Also applies to this vulnerability.

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 privileges on the target site, and no interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in MStore API < 3.9.7 takes a caller who can reach the endpoint. 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 3.9.7: builds < 3.9.7 are affected, anything from 3.9.7 onward is not.

Remediation

Update to version 3.9.7, 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 3.9.7 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-3131https://www.wordfence.com/threat-intel/vulnerabilities/id/7a747542-0601-4fa5-a97c-c72d1347013bhttps://nvd.nist.gov/vuln/detail/CVE-2023-3131

Related records

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