Mstore ApiWordPress extension · Inspireui
CVE-2023-3277
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 · uneditedThe MStore API plugin for WordPress is vulnerable to Unauthorized Account Access and Privilege Escalation in versions up to, and including, 4.10.7 due to improper implementation of the Apple login feature. This allows unauthenticated attackers to log in as any user as long as they know the user's 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 confidenceThe MStore API WordPress plugin has a broken authentication flaw in its Apple login implementation. Attackers can bypass authentication entirely by providing any valid user's email address during the Apple login process, effectively gaining unauthorized access to those accounts and their privileges.
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
<= 4.10.7CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed MStore API versionNavigate to WordPress admin > Plugins and locate MStore API to read the installed version number, or inspect the plugin header in the main plugin fileAffected if Installed version is 4.10.7 or lower
-
Confirm Apple login feature is enabledAccess the MStore API plugin settings in WordPress admin and check whether the Apple login option is turned onAffected if Apple login is enabled in plugin settings
-
Audit authentication logs for Apple login anomaliesReview server access logs and WordPress audit logs for Apple login API endpoint requests, looking for unusual patterns or unauthorized access attemptsAffected if Suspicious Apple login activity is found in logs
Environment is vulnerable if MStore API version is 4.10.7 or lower AND Apple login feature is enabled
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate MStore API to version 4.10.8 or later which contains the patched Apple login implementation, or disable the Apple login feature until patching is possible.
MStore API version 4.10.8 or later
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find the 'MStore API' plugin in the list
- Check if the current version is 4.10.7 or lower
- If vulnerable, click 'Update Now' to install the latest version
- Alternatively, download the updated plugin from the WordPress Plugin Repository and upload it manually
- After updating, verify the plugin version shows a version newer than 4.10.7
- Confirm the Apple login functionality still works as expected for legitimate users
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Mstore Api
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-3277 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-3277 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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