Maanstore ApiWordPress extension · Maantheme
CVE-2024-50487
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 · uneditedAuthentication Bypass Using an Alternate Path or Channel vulnerability in Acnoo MaanStore API maanstore-api allows Authentication Bypass.This issue affects MaanStore API: from n/a through <= 1.0.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 confidenceThe Acnoo MaanStore API versions up to 1.0.1 contain an authentication bypass vulnerability allowing attackers to access the API through an alternate path or channel without valid credentials. This critical flaw enables unauthenticated remote attackers to potentially view, modify, or delete data accessible through the API.
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
Maanstore ApiWordPress extension
<= 1.0.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
- 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 the installed MaanStore API versionLocate the theme or plugin version file. For WordPress/WooCommerce setups, check the style.css header or plugin main file for the 'Version' defined constant. For other frameworks, locate the package.json, composer.json, or equivalent metadata file where the Maanstore Api version is declared.Affected if The version listed is 1.0.1 or lower.
-
Confirm API endpoint exposureIdentify the API base URL endpoint used by MaanStore (typically /api/ or /wp-json/maanstore/ for WordPress installations). Attempt a GET request to a known API endpoint such as /api/products or /api/orders without providing any Authorization header or authentication token.Affected if The API returns valid JSON data or successful HTTP status (200/201) without requiring any credentials.
-
Verify authentication enforcement on all API routesUse a tool like curl or Postman to send requests to multiple MaanStore API endpoints (e.g., /api/users, /api/settings, /api/orders) without authentication credentials. Capture and inspect the HTTP response code and body for each.Affected if Any endpoint returns data or accepts requests without rejecting with 401 Unauthorized or 403 Forbidden.
-
Inspect authentication configuration filesCheck configuration files in the Maanstore Api installation directory for any authentication middleware, guard definitions, or route protection settings. Look for files named auth.php, middleware.php, api.php, or similar that define access control rules.Affected if No authentication middleware is defined, or authentication checks are commented out, missing, or conditionally bypassed for certain routes.
A user is affected if the MaanStore API version is 1.0.1 or lower AND the API endpoints are accessible without providing valid authentication credentials.
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 dataUpgrade MaanStore API to a patched version beyond 1.0.1 that addresses the authentication bypass, and conduct a security review of all authentication mechanisms and access control paths.
Fix this in Maanstore Api
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50487 — 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-2024-50487 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