Stacks Mobile App BuilderWordPress extension · Stacksmarket
CVE-2024-50527
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 · uneditedUnrestricted Upload of File with Dangerous Type vulnerability in Stacks Stacks Mobile App Builder stacks-mobile-app-builder allows Upload a Web Shell to a Web Server.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 · high confidenceThe Stacks Mobile App Builder plugin for WordPress contains an unrestricted file upload vulnerability that allows authenticated attackers to upload malicious PHP files (web shells) directly to the web server. Due to the lack of proper file type validation and extension checking, uploaded files can be executed, providing remote code execution capabilities and complete server compromise.
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.
-
Verify Stacks Mobile App Builder is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Stacks Mobile App Builder' by Stacksmarket. Alternatively, check the /wp-content/plugins/ directory for a folder named 'stacks-mobile-app-builder' or similar.Affected if The plugin is present on the WordPress site
-
Check the installed plugin versionIn WordPress admin Plugins list, find Stacks Mobile App Builder and note the version number displayed. Or inspect the plugin's main PHP file header for 'Version:' tag.Affected if The installed version is 5.2.3 or lower
-
Determine if file upload functionality is accessible to authenticated usersCheck if any user role (subscriber, contributor, author, editor) has access to the mobile app builder's upload features. Review plugin settings under the plugin's admin menu for any upload-related configuration.Affected if Authenticated users with lower privileges (subscriber/contributor) can access file upload functionality
-
Verify uploads directory allows script executionCheck the wp-content/uploads directory for .htaccess rules or Nginx config that prevents PHP execution. Look for directives like 'php_flag engine off' or 'deny from all' for PHP files.Affected if Upload directories allow execution of uploaded PHP files (no security restrictions in place)
The site is affected if Stacks Mobile App Builder version 5.2.3 or lower is installed AND the file upload feature is accessible to authenticated attackers AND the uploads directory permits script execution.
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 dataImmediately update to the latest version of Stacks Mobile App Builder once available. In the interim, disable the plugin or restrict file upload functionality to trusted users only. Implement server-side file type validation, whitelist allowed extensions, store uploads outside webroot, and disable script execution in upload directories.
Fix this in Stacks Mobile App Builder
Scoped from the published advisory
- Consultation3.0 h
- Implementation8.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50527 — 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-50527 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