dbcve.org
Wp Gravity Forms SalesforceWordPress extension · Crmperks

CVE-2025-60180

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-18
Fix available
A fix is available. Upgrade to 1.5.2 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Deserialization of Untrusted Data vulnerability in CRM Perks WP Gravity Forms Salesforce gf-salesforce-crmperks allows Object Injection.This issue affects WP Gravity Forms Salesforce: from n/a through <= 1.5.1.

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

The WP Gravity Forms Salesforce plugin (gf-salesforce-crmperks) contains a PHP Object Injection vulnerability due to unsafe deserialization of untrusted data. The plugin deserializes user-controlled input without proper validation, allowing attackers to inject malicious PHP objects and potentially achieve remote code execution.

MitigationUpgrade to a patched version of WP Gravity Forms Salesforce that properly validates or replaces unsafe unserialize() calls with safer alternatives like JSON encoding. If no patch is available, remove or disable the plugin until a fix is released.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wp Gravity Forms SalesforceWordPress extension
Affected:< 1.5.2

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
High
Integrity
High
Availability
High

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

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. Confirm plugin installation
    In WordPress admin, navigate to Plugins > Installed Plugins and look for 'Crmperks Wp Gravity Forms Salesforce' or 'Gravity Forms Salesforce' by Crmperks. Note if it is installed and activated.
    Affected if The plugin is installed and active in WordPress.
  2. Identify installed version
    In the WordPress Plugins list, click on the plugin to view details, or check the plugin header comment in its main PHP file for the 'Version' field. Common plugin directory paths include /wp-content/plugins/wp-gravityforms-salesforce/ or similar.
    Affected if The installed version is lower than 1.5.2.
  3. Search for unsafe deserialization calls
    Access the plugin files via FTP or file manager. Search within the plugin directory for patterns like 'unserialize(' without 'json_decode' or validation wrappers. Check PHP files that handle form submissions or Salesforce sync functionality.
    Affected if The plugin code contains unserialize() calls handling untrusted or user-supplied data without prior validation.
  4. Verify data input points
    Review forms or endpoints where external data enters the plugin, such as form field submissions, webhook receivers, or API integration points that feed data to deserialization functions.
    Affected if The plugin processes serialized data from unauthenticated or external sources.

You are affected if the Crmperks Wp Gravity Forms Salesforce plugin is installed with a version below 1.5.2 and contains unserialize() calls handling untrusted input.

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
Upgrade available Upgrade to 1.5.2 or later
Fixed in 1.5.2
Interim mitigation

Upgrade to a patched version of WP Gravity Forms Salesforce that properly validates or replaces unsafe unserialize() calls with safer alternatives like JSON encoding. If no patch is available, remove or disable the plugin until a fix is released.

Recommended fix High confidence

1.5.2

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'WP Gravity Forms Salesforce' (also known as gf-salesforce-crmperks) in the plugin list
  4. 4. If an update is available, click 'Update Now' to upgrade to version 1.5.2
  5. 5. Alternatively, navigate to Dashboard > Updates and select the plugin to update
  6. 6. After updating, verify the plugin version shows 1.5.2

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

Fix this in Wp Gravity Forms Salesforce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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