dbcve.org
Wp Gravity Forms HubspotWordPress extension · Crmperks

CVE-2025-60178

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-18
Fix available
A fix is available. Upgrade to 1.2.7 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 HubSpot gf-hubspot allows Object Injection.This issue affects WP Gravity Forms HubSpot: from n/a through <= 1.2.6.

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 · high confidence

A deserialization vulnerability in the WP Gravity Forms HubSpot plugin (gf-hubspot <= 1.2.6) allows unauthenticated attackers to inject PHP objects, potentially leading to remote code execution via object injection gadget chains.

MitigationUpdate WP Gravity Forms HubSpot to the latest version (>1.2.6) immediately, as this is a trivially exploitable unauthenticated vulnerability with critical CVSS 9.8 rating.

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 HubspotWordPress extension
Affected:< 1.2.7

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 is installed
    Check if the gf-hubspot or hubspot folder exists in /wp-content/plugins/ by listing the plugins directory or querying the WordPress database
    Affected if The plugin folder gf-hubspot or crmperks-gravity-forms-hubspot is present in the plugins directory
  2. Identify exact plugin version
    Open the main plugin PHP file (e.g., gf-hubspot.php) and look for the Version header in the plugin comment block, or check the readme.txt file for the Version field
    Affected if The reported version is 1.2.6 or lower, or if no version is displayed the plugin has not been updated past the vulnerable release
  3. Check plugin activation status
    Use WordPress admin plugins page, query wp_options table for active_plugins option, or run: wp plugin list --status=active --name=gf-hubspot
    Affected if The plugin shows as active or is listed in the active_plugins WordPress option; an inactive plugin cannot be exploited
  4. Verify deserialization input points
    Review plugin source code for unserialize() calls on user-controlled data such as $_GET, $_POST, or $_REQUEST parameters
    Affected if The plugin contains unserialize() calls that process external input without prior validation (this confirms the attack surface exists)
  5. Inspect network exposure
    Check if the WordPress site is publicly accessible and whether the /wp-content/plugins/gf-hubspot/ directory is reachable via HTTP
    Affected if The vulnerable plugin is active on a publicly accessible site, making the unauthenticated deserialization reachable from the internet

You are affected if the WP Gravity Forms HubSpot plugin is installed, active, and running at version 1.2.6 or lower on a publicly accessible WordPress site.

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.2.7 or later
Fixed in 1.2.7
Interim mitigation

Update WP Gravity Forms HubSpot to the latest version (>1.2.6) immediately, as this is a trivially exploitable unauthenticated vulnerability with critical CVSS 9.8 rating.

Recommended fix High confidence

1.2.7

  1. Backup your WordPress site database and files before making any changes
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate the 'WP Gravity Forms HubSpot' (gf-hubspot) plugin
  4. Click 'Update now' if an update is available, or manually download version 1.2.7 from the WordPress plugin repository/vendor and upload it
  5. Verify the plugin version shows 1.2.7 after updating
  6. Test that Gravity Forms HubSpot integration continues to function correctly (form submissions sync properly)
  7. Clear any caching layers if applicable

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

Fix this in Wp Gravity Forms Hubspot Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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