dbcve.org
Wp Gravity Forms Constant Contact PluginWordPress extension · Crmperks

CVE-2025-60174

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-18
Fix available
A fix is available. Upgrade to after 1.1.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 Constant Contact Plugin gf-constant-contact allows Object Injection.This issue affects WP Gravity Forms Constant Contact Plugin: from n/a through <= 1.1.2.

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

The gf-constant-contact WordPress plugin for Gravity Forms contains a deserialization vulnerability where untrusted user input is being passed to PHP's unserialize() function. This allows an attacker to craft malicious serialized PHP objects that can trigger magic methods to achieve remote code execution. The vulnerability affects all versions up to and including 1.1.2.

MitigationReplace any insecure deserialization of user input (unserialize()) with safer alternatives like JSON encoding, implement proper input validation, and update to the latest patched version when released by the vendor.

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 Constant Contact PluginWordPress extension
Affected:<= 1.1.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. Identify if the plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'gf-constant-contact', 'crmperks-gf-constant-contact', or similar constant-contact related folders from Crmperks.
    Affected if The plugin folder exists in the WordPress plugins directory
  2. Check the installed plugin version
    Open the main plugin PHP file (usually named the same as the folder) or the readme.txt file within the plugin directory and locate the version number declared in the plugin header.
    Affected if The version number displayed is 1.1.2 or lower (any version up to and including 1.1.2)
  3. Locate the vulnerable unserialize() call
    Search all PHP files within the plugin directory for the pattern 'unserialize(' - specifically look for instances where $_POST, $_GET, $_REQUEST, or other user input sources are passed directly to unserialize().
    Affected if PHP files contain unserialize() calls processing untrusted user input without prior sanitization
  4. Verify the plugin is active
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins, or query the wp_options table for the active_plugins option to check if the plugin is currently enabled.
    Affected if The plugin shows as active in WordPress and the vulnerable code is present

You are affected if the Crmperks Gravity Forms Constant Contact plugin is installed, active, and running version 1.1.2 or lower with the vulnerable unserialize() function 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 a release after 1.1.2
Interim mitigation

Replace any insecure deserialization of user input (unserialize()) with safer alternatives like JSON encoding, implement proper input validation, and update to the latest patched version when released by the vendor.

Recommended fix Moderate confidence

Latest available version of WP Gravity Forms Constant Contact Plugin (vendor should be contacted to confirm the specific fixed release)

  1. Check the WordPress admin dashboard for plugin updates under Plugins > All Plugins
  2. Update the WP Gravity Forms Constant Contact Plugin to the latest available version
  3. After updating, verify the new version number in the plugin list to confirm the update was applied
  4. Review the plugin's changelog or the vendor's website to confirm the security fix is included in the installed version
  5. If automatic updates are not enabled, consider enabling them for this plugin or implementing a manual update monitoring process

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

Fix this in Wp Gravity Forms Constant Contact Plugin Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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