Stacks Mobile App BuilderWordPress extension · Stacksmarket
CVE-2024-50477
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 Stacks Stacks Mobile App Builder stacks-mobile-app-builder allows Authentication Bypass.This issue affects Stacks Mobile App Builder: from n/a through <= 5.2.3.
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 confidenceStacks Mobile App Builder versions up to 5.2.3 contain an authentication bypass vulnerability allowing attackers to bypass authentication mechanisms through an alternate path or channel. This critical flaw (CVSS 9.8) enables unauthorized access to the mobile app builder's administrative or user functions without valid credentials.
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
Stacks Mobile App BuilderWordPress extension
<= 5.2.3CVSS 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 version of Stacksmarket Stacks Mobile App BuilderLocate the plugin/component version information through your CMS or WordPress plugin admin interface, or check the version metadata in the plugin files if you have file system accessAffected if The version is 5.2.3 or lower
-
Confirm the product is active on your siteCheck whether the Stacks Mobile App Builder plugin or component is installed and enabled in your applicationAffected if The plugin is installed and active with a version <= 5.2.3
-
Review authentication endpoints and pathsExamine your web server logs and application routing configuration for any mobile app builder endpoints that may accept requests without requiring valid authentication credentialsAffected if Mobile app builder endpoints are reachable without authentication tokens or session validation
-
Test for unauthenticated accessIf you have a staging or test environment, attempt to access mobile app builder functionality using requests without authentication headers or credentialsAffected if The application allows access to mobile app builder features without providing valid credentials
-
Audit authentication configuration filesReview any configuration files or settings related to the Stacks Mobile App Builder authentication module for any misconfigurations or bypass mechanismsAffected if The authentication configuration shows unusual settings or allows alternate paths
Your environment is affected if Stacksmarket Stacks Mobile App Builder version 5.2.3 or lower is installed and active, enabling potential unauthenticated access through alternate paths or channels.
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 to a patched version of Stacks Mobile App Builder beyond 5.2.3; if no patched version is available, implement additional authentication controls such as multi-factor authentication, IP allowlisting, or Web Application Firewall rules to restrict unauthorized access.
Fix this in Stacks Mobile App Builder
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50477 — 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-50477 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