CVE-2021-24148

MStore API <= 3.1.9 - Authentication Bypass

2021-02-02 00:00

Strategic Overview

Status: Patched in 3.2.0
Affected Plugin: MStore API – Create Native Android & iOS Apps On The Cloud
Affected Version: <= 3.1.9
CVSS: 9.8Critical
Weakness type: CWE-288 · Authentication Bypass Using an Alternate Path or Channel
CVE: CVE-2021-24148

View all MStore API – Create Native Android & iOS Apps On The Cloud vulnerabilities

At a glance

CVE-2021-24148 is a critical-severity Authentication Bypass Using an Alternate Path or Channel vulnerability in the MStore API WordPress plugin, affecting versions <= 3.1.9. 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.2.0; sites on affected versions should update now. Disclosed February 2021, reported by Vincent Datrier.

Vulnerability Overview

A business logic issue in the MStore API WordPress plugin, versions before 3.2.0, had an authentication bypass with Sign In With Apple allowing unauthenticated users to recover an authentication cookie with only an email address.

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-288: Authentication Bypass Using an Alternate Path or Channel

Reaching this weakness in MStore API <= 3.1.9 takes a caller who can reach the endpoint. Authentication bypass through an alternate path means the application has a second route to a protected action that skips the checks the primary route performs.

The protection on the main path becomes irrelevant, because the attacker simply uses the route that never asks. For MStore API the fix is 3.2.0: builds <= 3.1.9 are affected, anything from 3.2.0 onward is not.

Remediation

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

Login Security
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2021-24148 https://www.wordfence.com/threat-intel/vulnerabilities/id/16e3ca1b-817d-4f03-92ae-346a56271c47 https://nvd.nist.gov/vuln/detail/CVE-2021-24148

Related records

Same weakness class

Other vulnerabilities in MStore API – Create Native Android & iOS Apps On The Cloud

CVSS Vector

9.8

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/