CVE-2025-24772
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in cmsMinds Pay with Contact Form 7 pay-with-contact-form-7 allows Cross Site Request Forgery.This issue affects Pay with Contact Form 7: from n/a through <= 1.0.4.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the cmsMinds Pay with Contact Form 7 WordPress plugin (versions through 1.0.4). The vulnerability allows attackers to trick authenticated users into performing unintended actions, such as submitting form data or modifying settings, by exploiting the lack of proper anti-CSRF token validation on 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
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify plugin installation and versionNavigate to WordPress Admin > Plugins > Installed Plugins and look for 'cmsMinds Pay with Contact Form 7' in the list. Note the version number displayed under the plugin name.Affected if The plugin is installed and the version shown is 1.0.4 or lower.
-
Check plugin file for nonce validationAccess the plugin files via FTP or file manager. Locate the main plugin file (typically in wp-content/plugins/pay-with-contact-form-7/) and search for 'wp_nonce' or 'check_admin_referer' function calls in files handling form submissions or AJAX requests.Affected if No wp_nonce_field, wp_nonce_url, or check_admin_referer calls are found in form handling files, indicating missing CSRF protection.
-
Inspect AJAX handlers for nonce verificationIn the plugin directory, examine PHP files containing 'wp_ajax_' or 'wp_ajax_nopriv_' hooks. Verify if these handlers call wp_verify_nonce or check_ajax_referer before processing requests.Affected if AJAX handlers process requests without verifying a nonce, meaning attackers can trigger actions via forged requests.
-
Identify exposed form endpointsCheck plugin files for add_action calls on 'init', 'admin_init', or form shortcode handlers. Look at form action URLs and determine if they point to admin-ajax.php or custom endpoints without nonce parameters.Affected if Forms submit to endpoints without including a nonce token as a hidden field or URL parameter.
A user is affected if the cmsMinds Pay with Contact Form 7 plugin (version 1.0.4 or below) is installed and its form processing code lacks WordPress nonce validation.
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 dataImplement WordPress nonces (anti-CSRF tokens) on all form submissions and AJAX handlers, validate the nonce before processing any state-changing requests, and ensure SameSite cookie attributes are properly configured.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2025-24772 — 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-2025-24772 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