dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-49330

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Integration for Contact Form 7 and Zoho CRM, Bigin cf7-zoho allows Object Injection.This issue affects Integration for Contact Form 7 and Zoho CRM, Bigin: from n/a through <= 1.3.0.

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 CRM Perks cf7-zoho plugin <= 1.3.0 has a deserialization vulnerability where untrusted data is unsafely processed, allowing attackers to inject arbitrary PHP objects. Depending on what classes exist in the plugin, this could enable remote code execution via magic method invocation.

MitigationUpdate to a patched version of the plugin (> 1.3.0) immediately. If no patch is available, disable the plugin and consider alternative CRM integration solutions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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. Locate the cf7-zoho plugin installation
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named cf7-zoho, cf7-zoho-crm, or similar. Also check the WordPress admin plugin list.
    Affected if The plugin folder exists in the WordPress installation
  2. Identify the installed version
    Open the main plugin PHP file (usually named cf7-zoho.php or similar in the plugin folder) and locate the plugin header comment containing 'Version:' or check the version recorded in WordPress admin under Plugins > Installed Plugins.
    Affected if The version listed is 1.3.0 or lower
  3. Determine if the plugin is active
    In WordPress admin, navigate to Plugins > Installed Plugins and verify whether the cf7-zoho plugin is activated.
    Affected if The plugin is currently active and processing form submissions
  4. Assess exposure to untrusted input
    Examine if the plugin is configured to receive form submissions from the public. If Contact Form 7 forms are set up to send data to Zoho via this plugin, the deserialization endpoint is reachable.
    Affected if CF7 forms are configured to use the plugin for CRM integration and are publicly accessible

A user is affected if the cf7-zoho plugin is installed, active, and running version 1.3.0 or lower while processing external form submissions.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version of the plugin (> 1.3.0) immediately. If no patch is available, disable the plugin and consider alternative CRM integration solutions.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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