dbcve.org
Wp Gravity Forms InsightlyWordPress extension · Crmperks

CVE-2025-60090

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

Object Injection vulnerability in WP Gravity Forms Insightly plugin allows attackers to inject malicious PHP objects via unsafe deserialization. This can lead to remote code execution if PHP magic methods or POP chains exist in the application.

MitigationUpdate WP Gravity Forms Insightly to the latest version; if unavailable, disable the plugin or implement input validation/safe deserialization methods (e.g., json_decode instead of unserialize).

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 InsightlyWordPress extension
Affected:< 1.1.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
    Navigate to WordPress admin > Plugins and locate 'Crmperks Wp Gravity Forms Insightly' or check the plugins directory for the insightly-related plugin files
    Affected if The plugin is present on the WordPress site
  2. Identify installed version
    In WordPress admin > Plugins, click on the plugin details to view the installed version number, or inspect the plugin's main PHP file for the 'Version' header in the plugin comment block
    Affected if Version is less than 1.1.7 (e.g., 1.1.6, 1.1.5, etc.)
  3. Locate unsafe unserialize calls
    Using a file search or grep tool, scan the plugin directory for 'unserialize' patterns in PHP files. Examine each occurrence to determine if it processes data that could be user-controlled
    Affected if The plugin contains unserialize() calls that handle input from $_GET, $_POST, $_REQUEST, or similar user-supplied sources
  4. Verify data source for deserialization
    Trace the data flow from any unserialize() call found. Check if the data originates from form fields, API endpoints, URL parameters, or other external inputs that attackers could manipulate
    Affected if User-controllable data flows into an unserialize() call without prior validation or safe encoding

A site is affected if the Crmperks WP Gravity Forms Insightly plugin version is below 1.1.7 and contains unserialize() calls that process untrusted user input from form submissions or other external sources.

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.1.7 or later
Fixed in 1.1.7
Interim mitigation

Update WP Gravity Forms Insightly to the latest version; if unavailable, disable the plugin or implement input validation/safe deserialization methods (e.g., json_decode instead of unserialize).

Recommended fix High confidence

WP Gravity Forms Insightly version 1.1.7

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'WP Gravity Forms Insightly' (or 'gf-insightly') plugin
  4. Check the current version to confirm it is <= 1.1.6
  5. Click 'Update now' if an update to version 1.1.7 is available, or manually upload version 1.1.7 of the plugin
  6. After updating, verify the plugin version shows 1.1.7

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

Fix this in Wp Gravity Forms Insightly Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
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,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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