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

CVE-2025-24001

HIGH · 7.1 CVSS v3.1 Published 2025-01-21
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 Ngô Thắng IT PPO Call To Actions ppo-call-to-actions allows Cross Site Request Forgery.This issue affects PPO Call To Actions: from n/a through <= 0.1.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

Cross-Site Request Forgery (CSRF) vulnerability in the PPO Call To Actions WordPress plugin (versions <= 0.1.3) allows attackers to induce authenticated users to perform unintended actions by tricking them into submitting malicious requests, potentially modifying plugin settings or call-to-action configurations.

MitigationImplement anti-CSRF tokens (nonce validation) on all state-changing actions and forms within the plugin, and ensure proper referrer validation. Consider adding SameSite cookie attributes and requiring re-authentication for sensitive operations.

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 PPO Call To Actions plugin is installed
    Log into WordPress admin panel, navigate to Plugins > Installed Plugins, and search for 'PPO Call To Actions' or 'ppo-call-to-actions' in the plugin list. Also check the /wp-content/plugins/ directory for a folder named 'ppo-call-to-actions' or similar.
    Affected if The plugin folder exists in the plugins directory or is listed in the WordPress admin plugins page
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find PPO Call To Actions, and note the version number displayed. Alternatively, open the main plugin PHP file (usually in /wp-content/plugins/ppo-call-to-actions/) and look for the 'Version' header in the plugin comment block.
    Affected if The displayed version is 0.1.3 or any version lower (e.g., 0.1.2, 0.1.1, 0.1.0)
  3. Identify state-changing admin actions in the plugin
    Examine PHP files in the plugin directory for form submissions and URL actions that modify data (search for $_POST, $_GET, admin_post, and action parameters). Common patterns include settings saves, CTA creation/editing/deletion, or configuration updates.
    Affected if The plugin contains forms or URL handlers that perform database writes, settings changes, or configuration updates
  4. Verify nonce validation on state-changing actions
    Search the plugin PHP files for nonce validation functions: wp_nonce_field, wp_nonce_url, check_admin_referer, check_ajax_referer, or wp_verify_nonce. Examine each state-changing form or action handler found in step 3 to confirm a valid nonce check exists before processing.
    Affected if State-changing forms or actions lack nonce verification, or the nonce check is missing/incorrect before performing sensitive operations
  5. Check referrer validation on admin requests
    Look for check_admin_referer calls in the plugin's admin-handling code, or verify that WordPress nonces are being used as an alternative form of CSRF protection.
    Affected if No referrer validation or nonce protection exists on sensitive admin actions

You are affected if the PPO Call To Actions plugin is installed at version 0.1.3 or lower AND contains state-changing actions (forms, settings saves, or data modifications) that lack nonce or referrer validation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens (nonce validation) on all state-changing actions and forms within the plugin, and ensure proper referrer validation. Consider adding SameSite cookie attributes and requiring re-authentication for sensitive operations.

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-2025-24001 — 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-2025-24001 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