CVE-2026-57375
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 · uneditedMissing Authorization vulnerability in FluxBuilder MStore API mstore-api allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects MStore API: from n/a through <= 4.18.4.
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 confidenceMissing Authorization vulnerability in FluxBuilder MStore API allows attackers to access resources or perform actions without proper authentication verification due to incorrectly configured access control security levels. This broken access control issue affects all API endpoints in versions up to and including 4.18.4, potentially allowing unauthorized users to bypass permission checks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
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.
-
Confirm FluxBuilder MStore API is installedIdentify whether the FluxBuilder MStore API component is present in your environment by reviewing your application dependencies, plugins list, or installed software inventoryAffected if FluxBuilder MStore API is present in the environment
-
Determine the installed versionCheck the installed version of FluxBuilder MStore API by reviewing your software documentation, version file, or dependency manifest (package.json, composer.json, or similar)Affected if The installed version is 4.18.4 or lower
-
Identify accessible API endpointsReview your API documentation or enumerate available endpoints to determine which FluxBuilder MStore API routes are exposedAffected if Any FluxBuilder MStore API endpoints are accessible
-
Test API access without authenticationAttempt to access FluxBuilder MStore API endpoints using unauthenticated requests (no API key, token, or session credentials)Affected if API requests succeed without requiring authentication credentials
-
Verify access control configurationInspect the access control or authorization configuration settings for the FluxBuilder MStore API to determine if role-based or permission checks are enforced on endpointsAffected if Access control rules are missing, misconfigured, or not enforced on API endpoints
The environment is affected if FluxBuilder MStore API version 4.18.4 or lower is installed AND its API endpoints can be accessed without authentication due to missing or broken access control enforcement.
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 proper role-based access control (RBAC) and authorization checks on all API endpoints to verify user permissions before granting access to protected resources. Conduct a comprehensive audit of access control configurations.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57375 — 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-2026-57375 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