CVE-2025-54682
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 CRM Perks Connector for Gravity Forms and Google Sheets wp-gravity-forms-spreadsheets allows Cross Site Request Forgery.This issue affects Connector for Gravity Forms and Google Sheets: from n/a through <= 1.2.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 CRM Perks Connector for Gravity Forms and Google Sheets WordPress plugin (wp-gravity-forms-spreadsheets) allows attackers to trick authenticated users into performing unintended actions via maliciously crafted requests. The vulnerability exists in versions up to and including 1.2.4, likely due to missing anti-CSRF token validation on form submissions or AJAX endpoints.
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.
-
Identify installed plugin versionNavigate to WordPress admin > Plugins > Installed Plugins, locate 'CRM Perks Connector for Gravity Forms and Google Sheets' (wp-gravity-forms-spreadsheets), and note the version number displayed. Alternatively, check the plugin header in wp-content/plugins/wp-gravity-forms-spreadsheets/wp-gravity-forms-spreadsheets.php for the 'Version:' tag.Affected if Version is 1.2.4 or lower
-
Confirm plugin is activeVerify the plugin is enabled on your WordPress site. Go to Plugins > Installed Plugins and check if the plugin shows an 'Active' status.Affected if Plugin is active and version is 1.2.4 or lower
-
Inspect AJAX handlers for nonce validationSearch plugin PHP files for AJAX action hooks (add_action('wp_ajax_...') or add_action('wp_ajax_nopriv_...')) and verify if each includes check_ajax_referer() or wp_verify_nonce() before processing requests. Check files like class-gf-spreadsheet-connector.php or similar handler files.Affected if AJAX endpoints lack nonce verification (check_ajax_referer or wp_verify_nonce)
-
Inspect form submissions for nonce fieldsReview PHP files handling form submissions (likely in main plugin file or gravityforms folder) to check if wp_nonce_field() is called when generating forms, and if wp_verify_nonce() or check_admin_referer() validates the nonce upon submission.Affected if Form handlers do not validate nonces
Your environment is affected if the CRM Perks Connector for Gravity Forms and Google Sheets plugin is active at version 1.2.4 or lower, and AJAX endpoints or form submissions lack WordPress nonce verification.
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 forms and AJAX actions within the plugin, and verify nonce validation on the server side before processing requests. Users should update to a patched version once available.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54682 — 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-54682 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