CVE-2023-50878

MStore API <= 4.10.1 - Cross-Site Request Forgery

2023-12-26 00:00
Kévin Mosbahi (Mika)

Strategic Overview

Status
Patched in 4.10.2
Affected Version
<= 4.10.1
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-50878
View all MStore API – Create Native Android & iOS Apps On The Cloud vulnerabilities

At a glance

CVE-2023-50878 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the MStore API WordPress plugin, affecting versions <= 4.10.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.10.2; sites on affected versions should update now. Disclosed December 2023, reported by Kévin Mosbahi (Mika).

Vulnerability Overview

The MStore API plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to 4.10.2 (exclusive). This is due to missing or incorrect nonce validation in the templates/admin/mstore-api-admin-dashboard.php file. This makes it possible for unauthenticated attackers to upload an Apple key file via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in MStore API <= 4.10.1 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For MStore API the fix is 4.10.2: builds <= 4.10.1 are affected, anything from 4.10.2 onward is not.

Remediation

Update to version 4.10.2, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to MStore API: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: MStore API 4.10.2 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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