Mstore ApiWordPress extension · Inspireui
CVE-2023-50878
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in InspireUI MStore API.This issue affects MStore API: from n/a through 4.10.1.
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 · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in InspireUI MStore API allows attackers to induce authenticated users to perform unintended actions. The vulnerability exists in versions through 4.10.1, potentially enabling attackers to execute malicious requests on behalf of legitimate users without their knowledge.
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.1CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 the installed MStore API versionLocate the version information in your MStore API installation (check package.json, plugin metadata, or admin dashboard version display) and compare it to the affected range of <= 4.10.1Affected if The installed version is 4.10.1 or any earlier version
-
Identify exposed state-changing endpointsReview your MStore API deployment for endpoints that handle user authentication and perform actions (POST, PUT, DELETE requests) such as user management, order processing, or cart operationsAffected if State-changing endpoints are accessible without additional CSRF protection mechanisms
-
Verify absence of anti-CSRF token implementationInspect the codebase or API configuration for anti-CSRF token generation, storage, and validation logic on state-changing endpoints. Check if endpoints require a valid token parameter or header with each requestAffected if No anti-CSRF token validation is implemented on state-changing endpoints
-
Check Origin and Referer header validationExamine server-side request handling to determine if incoming requests are validated against an allowed origin list or if Referer headers are verified before processing state-changing operationsAffected if Origin and Referer header validation is missing or not enforced on sensitive endpoints
You are affected if your MStore API version is 4.10.1 or earlier AND state-changing endpoints are exposed without anti-CSRF token validation or Origin/Referer header checks.
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.
From vendor dataImplement anti-CSRF tokens and validate request origins (Origin/Referer headers) on all state-changing endpoints to prevent CSRF attacks.
Fix this in Mstore Api
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-50878 — 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-50878 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