dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-12420

MEDIUM · 6.5 CVSS v3.1 Published 2024-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
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
The The WPMobile.App — Android and iOS Mobile Application plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 11.52. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes.

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 confidence

The WPMobile.App WordPress plugin fails to validate user-supplied input before passing it to do_shortcode(), allowing unauthenticated attackers to execute arbitrary shortcodes. This can expose sensitive data, escalate privileges, or lead to further compromise depending on registered shortcodes.

MitigationUpdate the plugin to version 11.53 or later where the vulnerability is patched. If immediate patching is not feasible, consider temporarily disabling the plugin or restricting access at the web server level.

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 checks

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

  1. Locate the WPMobile.App plugin installation
    Check your WordPress plugins directory (wp-content/plugins/) for a folder named 'wpmobile-app', 'wpmobile', 'wp-mobile-app', or similar. Also check the WordPress admin under Plugins > Installed Plugins for an entry named WPMobile.App, Push Notifications, or related.
    Affected if The plugin folder or entry is found on the system
  2. Identify the installed plugin version
    If found, open the plugin's main PHP file or readme.txt in the plugin folder and locate the version number in the plugin header comment (e.g., 'Version: x.x.x') or the 'Stable tag' field in readme.txt.
    Affected if The version number cannot be determined or is below 11.53
  3. Compare version against the patched release
    Take the installed version (e.g., 11.52, 11.50, etc.) and compare it to version 11.53. Any version lower than 11.53 is vulnerable.
    Affected if Installed version is lower than 11.53 (e.g., 11.52, 11.51, 11.50, etc.)
  4. Confirm the plugin is active
    In WordPress admin, verify if the WPMobile.App plugin shows as 'Active'. The vulnerability is exploitable when the plugin is installed and active, as do_shortcode() must be reachable.
    Affected if Plugin is active and version is below 11.53

If the WPMobile.App plugin is installed, active, and running a version lower than 11.53, your environment is affected by this CVE.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 11.53 or later where the vulnerability is patched. If immediate patching is not feasible, consider temporarily disabling the plugin or restricting access at the web server level.

Recommended fix Moderate confidence

Version 11.53 or later of the WPMobile.App plugin

  1. Update the WPMobile.App plugin to the latest available version (11.53 or later) via the WordPress plugin repository or your site's plugin management interface.
  2. After updating, verify that the arbitrary shortcode execution vulnerability is no longer present.
  3. Consider reviewing active shortcodes on your site to ensure no malicious shortcodes were added during any potential exploitation.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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-12420 — 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-12420 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