dbcve.org
Wp Gravity Forms Zoho Crm And BiginWordPress extension · Crmperks

CVE-2025-60091

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-18
Fix available
A fix is available. Upgrade to 1.3.0 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 Zoho CRM and Bigin gf-zoho allows Object Injection.This issue affects WP Gravity Forms Zoho CRM and Bigin: from n/a through <= 1.2.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

A deserialization of untrusted data vulnerability in the WP Gravity Forms Zoho CRM and Bigin plugin (gf-zoho) allows unauthenticated attackers to inject PHP objects through unsanitized input, potentially leading to remote code execution.

MitigationUpdate to the latest version of the WP Gravity Forms Zoho CRM and Bigin plugin; if no patched version is available, disable the plugin and seek alternative solutions.

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 Zoho Crm And BiginWordPress extension
Affected:< 1.3.0

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. Verify plugin is installed
    Check for the presence of the 'Crmperks WP Gravity Forms Zoho CRM and Bigin' plugin in the WordPress plugins directory (wp-content/plugins/), looking for a folder named 'gf-zoho' or containing 'zoho' in the name.
    Affected if The plugin folder exists in the WordPress plugins directory.
  2. Determine installed version
    Locate the plugin's main PHP file (typically index.php or a file named gf-zoho.php) and read the plugin version from the file header comment (look for 'Version: x.x.x'). Alternatively, check the readme.txt file for the 'Stable tag' or 'Version' entry.
    Affected if The installed version is less than 1.3.0 (e.g., 1.2.x, 1.1.x, 1.0.x).
  3. Confirm plugin is active
    In the WordPress admin dashboard, go to Plugins > Installed Plugins and verify whether the Crmperks WP Gravity Forms Zoho CRM and Bigin plugin is currently activated.
    Affected if The plugin is activated in the WordPress site.
  4. Check if Zoho integration features are in use
    Look for any Gravity Forms feeds or settings that connect to Zoho CRM or Bigin. This can be done via Gravity Forms > Settings > Zoho CRM (if available) or by checking for saved feeds containing 'zoho' as the feed type.
    Affected if Zoho CRM or Bigin feeds are configured and active in Gravity Forms.

The environment is affected if the Crmperks WP Gravity Forms Zoho CRM and Bigin plugin is installed, activated, and running a version lower than 1.3.0 with Zoho integration features enabled.

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.3.0 or later
Fixed in 1.3.0
Interim mitigation

Update to the latest version of the WP Gravity Forms Zoho CRM and Bigin plugin; if no patched version is available, disable the plugin and seek alternative solutions.

Recommended fix High confidence

1.3.0

  1. Backup your WordPress site database and files before making any changes
  2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. Find 'WP Gravity Forms Zoho CRM and Bigin' (gf-zoho) in the plugin list
  4. Click 'Update now' if an update is available, or manually upload version 1.3.0 of the plugin
  5. Verify the plugin is now running version 1.3.0 by checking the Plugins page
  6. Test that Gravity Forms integration with Zoho CRM continues to function normally

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

Fix this in Wp Gravity Forms Zoho Crm And Bigin Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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