MStore API < 3.4.5 - Arbitrary File Upload

2021-10-05 00:00
spacehen

Strategic Overview

Status
Patched in 3.4.5
Affected Plugin
MStore API – Create Native Android & iOS Apps On The Cloud
Affected Version
< 3.4.5
CVSS
9.8Critical
Weakness type
CWE-434 · Unrestricted Upload of File with Dangerous Type
CVE
CVE pending
View all MStore API – Create Native Android & iOS Apps On The Cloud vulnerabilities

At a glance

This record tracks a critical-severity Unrestricted Upload of File with Dangerous Type vulnerability in the MStore API WordPress plugin, affecting versions < 3.4.5. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.4.5; sites on affected versions should update now. Disclosed October 2021, reported by spacehen.

Vulnerability Overview

The MStore API plugin for WordPress is vulnerable to arbitrary file uploads due to missing authorization via the api/flutter_woo/config_file REST endpoint in versions before 3.4.5. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected sites server which may make remote code execution possible.

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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-434: Unrestricted Upload of File with Dangerous Type

Reaching this weakness in MStore API < 3.4.5 takes a caller who can reach the endpoint. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.

If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. For MStore API the fix is 3.4.5: builds < 3.4.5 are affected, anything from 3.4.5 onward is not.

Remediation

Update to version 3.4.5, 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. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: MStore API 3.4.5 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/04b7a2ba-e299-4781-8ee6-644938bf9629

Related records

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