CVE-2023-3202

MStore API <= 3.9.6 - Cross-Site Request Forgery to Firebase Server Key Update

2023-06-13 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.6
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-3202
View all MStore API – Create Native Android & iOS Apps On The Cloud vulnerabilities

At a glance

CVE-2023-3202 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the MStore API WordPress plugin, affecting versions <= 3.9.6. 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 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 Cross-Site Request Forgery due to missing nonce validation on the mstore_update_firebase_server_key function. This makes it possible for unauthenticated attackers to update the firebase server key to push notification when order status changed 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 <= 3.9.6 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 3.9.7: builds <= 3.9.6 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?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-3202https://www.wordfence.com/threat-intel/vulnerabilities/id/d2b3612e-3c91-469b-98ef-fdb03b0ee9d9https://nvd.nist.gov/vuln/detail/CVE-2023-3202

Related records

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