dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2024-54386

HIGH · 7.1 CVSS v3.1 Published 2024-12-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in pushmonkey Push Monkey Pro – Web Push Notifications and WooCommerce Abandoned Cart push-monkey-desktop-push-notifications allows Cross Site Request Forgery.This issue affects Push Monkey Pro – Web Push Notifications and WooCommerce Abandoned Cart: from n/a through <= 3.9.

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

Cross-Site Request Forgery (CSRF) vulnerability in the Push Monkey Pro WordPress plugin (versions <= 3.9). The plugin fails to properly validate anti-CSRF tokens on state-changing requests, allowing authenticated administrators to unknowingly execute unintended actions such as modifying push notification settings or processing abandoned cart data.

MitigationImplement WordPress nonces (anti-CSRF tokens) on all forms and AJAX endpoints that perform state-changing operations. Additionally, verify Origin and Referer headers server-side to prevent cross-origin requests.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

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. Verify Push Monkey Pro is installed
    Check your WordPress plugins directory or WordPress admin panel under Plugins to confirm Push Monkey Pro is installed and active
    Affected if Push Monkey Pro plugin is present in the WordPress installation
  2. Check installed version number
    View the plugin details in WordPress admin (Plugins > Installed Plugins > Push Monkey Pro) or inspect the main plugin file (push-monkey-pro.php) to find the version declaration
    Affected if Version is 3.9 or lower
  3. Inspect plugin for nonce validation
    Examine the plugin PHP files for WordPress nonce verification functions such as wp_verify_nonce(), check_admin_referer(), or nonce_field() on AJAX handlers and form processing code related to push notification settings and abandoned cart operations
    Affected if State-changing code paths lack nonce verification calls or the verification is missing/incorrect
  4. Check Origin and Referer header validation
    Review the plugin's request handling code to determine if server-side validation of Origin or Referer HTTP headers is performed before processing state-changing requests
    Affected if No Origin or Referer header validation exists in the plugin's request handling

Affected if Push Monkey Pro version 3.9 or lower is installed and the plugin fails to validate anti-CSRF tokens on its state-changing endpoints for push notification settings or abandoned cart processing.

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

Implement WordPress nonces (anti-CSRF tokens) on all forms and AJAX endpoints that perform state-changing operations. Additionally, verify Origin and Referer headers server-side to prevent cross-origin requests.

Recommended fix Moderate confidence

Latest available version higher than 3.9 (e.g., 4.0 or later if released)

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Find 'Push Monkey Pro – Web Push Notifications and WooCommerce Abandoned Cart'
  4. 4. Check if an update is available for this plugin
  5. 5. If an update is available, update to the latest version (version higher than 3.9)
  6. 6. Verify the update was successful after completion

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-54386 — 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-54386 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