Wp Gravity Forms Freshdesk PluginWordPress extension · Crmperks
CVE-2025-60089
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 · uneditedDeserialization of Untrusted Data vulnerability in CRM Perks WP Gravity Forms FreshDesk Plugin gf-freshdesk allows Object Injection.This issue affects WP Gravity Forms FreshDesk Plugin: from n/a through <= 1.3.5.
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 confidenceA deserialization vulnerability in the CRM Perks WP Gravity Forms FreshDesk plugin (gf-freshdesk) allows unauthenticated attackers to inject malicious PHP objects via untrusted data deserialization, potentially leading to remote code execution.
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 Freshdesk PluginWordPress extension
< 1.3.6CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate the CRM Perks WP Gravity Forms FreshDesk plugin installationCheck your WordPress wp-content/plugins directory for a folder named 'gf-freshdesk' or 'crmperks-gf-freshdesk'. If using a managed hosting panel, you may find this under the plugins section.Affected if The plugin folder exists on the server
-
Identify the installed plugin versionOpen the main plugin file (usually gf-freshdesk.php or index.php inside the plugin folder) and locate the plugin header comment which contains the Version field. Alternatively, check the WordPress plugin admin page under Plugins > Installed Plugins.Affected if The version number displayed is less than 1.3.6 or cannot be determined (older installations may not show version)
-
Verify if the plugin is active on the WordPress siteLog in to the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for the CRM Perks WP Gravity Forms FreshDesk plugin entry and confirm whether it shows as 'Active'.Affected if The plugin is currently active and the version is less than 1.3.6
-
Inspect plugin files for unauthorized modificationsUse file integrity scanning or manually compare plugin files against a clean installation from the WordPress repository or the vendor. Look for any added PHP files, encoded payloads, or backdoors.Affected if Unexpected files exist in the plugin directory or files have been modified without an official update
Your environment is affected if the CRM Perks WP Gravity Forms FreshDesk plugin is installed, active, and running a version numbered lower than 1.3.6.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.3.6
Update to the latest patched version of the WP Gravity Forms FreshDesk plugin immediately; if no patch is available, disable or remove the plugin until a fix is released.
1.3.6
- Backup your WordPress site and database before making any changes
- Navigate to Plugins > Installed Plugins in WordPress admin
- Find the 'WP Gravity Forms FreshDesk' plugin
- Click 'Update now' if an update is available, or manually upload version 1.3.6
- Verify the plugin version is now 1.3.6 after updating
- Test that Gravity Forms integration with FreshDesk still functions correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wp Gravity Forms Freshdesk Plugin
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60089 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-60089 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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