dbcve.org
Mstore ApiWordPress extension · Inspireui

CVE-2021-24148

CRITICAL · 9.8 CVSS v3.1 Published 2021-03-18
Fix available
A fix is available. Upgrade to 3.2.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The MStore API WordPress plugin before version 3.2.0 contains an authentication bypass vulnerability in its Sign In With Apple integration. Attackers can recover authentication cookies for any user account by providing only an email address, without needing to complete actual Apple authentication.

MitigationUpgrade MStore API to version 3.2.0 or later to remediate the authentication bypass vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mstore ApiWordPress extension
Affected:< 3.2.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify MStore API plugin is installed
    Navigate to WordPress admin > Plugins and look for 'MStore API' or 'mstore-api' in the plugins list, or check the file system at wp-content/plugins/ for a folder containing 'mstore' or 'mstore-api'
    Affected if MStore API plugin is not present in the WordPress installation
  2. Determine installed version of MStore API
    In WordPress admin > Plugins, click on the MStore API plugin to view its details and version number; alternatively, read the main plugin PHP file header which contains the 'Version' field
    Affected if The displayed version is less than 3.2.0 (for example, 3.1.9, 3.0.0, etc.)
  3. Confirm Sign In With Apple is enabled
    Navigate to WordPress admin > MStore API settings and look for Apple Sign In, Sign In With Apple, or Apple Login configuration options; check if any Apple-related authentication method is active
    Affected if Sign In With Apple integration is enabled or configured in the plugin settings
  4. Check for unauthorized authentication cookie generation
    Review WordPress access logs for requests to endpoints containing 'apple', 'signin', or 'auth' in the URL path with unusual parameters; look for POST requests to the MStore API authentication endpoints that succeed without valid Apple token validation
    Affected if Log analysis shows successful authentication attempts using email addresses without proper Apple token exchange

You are affected if MStore API version is below 3.2.0 AND the Sign In With Apple feature is enabled, allowing attackers to obtain authentication cookies with only an email address.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.2.0 or later
Fixed in 3.2.0
Interim mitigation

Upgrade MStore API to version 3.2.0 or later to remediate the authentication bypass vulnerability.

Recommended fix High confidence

MStore API version 3.2.0

  1. 1. Backup your WordPress site before making any changes
  2. 2. Navigate to the WordPress admin dashboard
  3. 3. Go to Plugins > Installed Plugins
  4. 4. Find the MStore API plugin in the list
  5. 5. If an update is available, click 'Update Now' to upgrade to version 3.2.0 or later
  6. 6. Alternatively, download version 3.2.0 or later from the WordPress plugin repository and upload/install it manually
  7. 7. After updating, verify the plugin version shows 3.2.0 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mstore Api Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-24148 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-24148 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data