dbcve.org
Stacks Mobile App BuilderWordPress extension · Stacksmarket

CVE-2024-50528

HIGH · 7.5 CVSS v3.1 Published 2024-11-04
Fix available
A fix is available. Upgrade to after 5.2.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Exposure of Sensitive System Information to an Unauthorized Control Sphere vulnerability in Stacks Stacks Mobile App Builder stacks-mobile-app-builder allows Retrieve Embedded Sensitive Data.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 confidence

The Stacks Mobile App Builder plugin for WordPress (versions <=5.2.3) contains an information disclosure vulnerability allowing unauthorized retrieval of embedded sensitive data. The vulnerability stems from improper access controls that expose system information or credentials embedded within the mobile app builder's configuration or output to unauthorized users, resulting in potential confidentiality compromise.

MitigationUpgrade Stacks Mobile App Builder to a version beyond 5.2.3. Additionally, audit the application for any inadvertently embedded sensitive data such as API keys, credentials, or configuration secrets and remove or properly secure them.

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
Affected:<= 5.2.3

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Stacks Mobile App Builder version
    Log into WordPress admin, navigate to Plugins > Installed Plugins, locate 'Stacks Mobile App Builder' or 'Stacksmarket Stacks Mobile App Builder', and check the version number displayed. Alternatively, check the plugin's main PHP file header for the Version field.
    Affected if The installed version is 5.2.3 or lower.
  2. Check for sensitive data in app builder configuration
    Review the plugin settings under the mobile app builder menu in WordPress admin. Look for fields that may contain API keys, credentials, tokens, or configuration secrets that could be embedded into the mobile app output.
    Affected if Any sensitive values such as API keys, passwords, tokens, or credentials are present in the plugin configuration.
  3. Inspect mobile app output endpoints
    If the plugin exposes REST API endpoints or generated app files, attempt to access them without authentication. Common paths include /wp-json/stacks-mobile/v1/ or similar app-related endpoints. Check if system information, configuration data, or credentials are returned.
    Affected if The endpoints return sensitive system information, credentials, or configuration data to unauthenticated users.
  4. Review app configuration export files
    If the plugin generates export files, configuration files, or app manifests, locate and inspect them for embedded secrets. Check the /wp-content/uploads/stacks-mobile/ or similar plugin directories for any publicly accessible generated files.
    Affected if Exported or generated files contain API keys, credentials, or other sensitive configuration data accessible without authentication.

A user is affected if the Stacks Mobile App Builder plugin version is 5.2.3 or lower AND sensitive data (API keys, credentials, tokens) is embedded in the plugin configuration or exposed through app output endpoints to unauthorized users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 5.2.3
Interim mitigation

Upgrade Stacks Mobile App Builder to a version beyond 5.2.3. Additionally, audit the application for any inadvertently embedded sensitive data such as API keys, credentials, or configuration secrets and remove or properly secure them.

Fix this in Stacks Mobile App Builder Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-50528 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-50528 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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