dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-7696

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-19
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
The Integration for Pipedrive and Contact Form 7, WPForms, Elementor, Ninja Forms plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.2.3 via deserialization of untrusted input within the verify_field_val() function. This makes it possible for unauthenticated attackers to inject a PHP Object. The additional presence of a POP chain in the Contact Form 7 plugin, which is likely to be used alongside, allows attackers to delete arbitrary files, leading to a denial of service or remote code execution when the wp-config.php file is deleted.

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 Integration for Pipedrive and Contact Form 7, WPForms, Elementor, Ninja Forms WordPress plugin up to version 1.2.3 contains a PHP Object Injection vulnerability in the verify_field_val() function through unsafe deserialization of untrusted input. This allows unauthenticated attackers to inject PHP objects. When combined with a POP chain present in Contact Form 7 (which is commonly used alongside this plugin), attackers can delete arbitrary files including wp-config.php, leading to denial of service or remote code execution.

MitigationUpdate the plugin to version 1.2.4 or later immediately. If immediate update is not possible, disable the plugin or implement WAF rules to block deserialization attack patterns at the web application layer.

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. Identify installed version of the Pipedrive integration plugin
    Locate the plugin folder (typically wp-content/plugins/pipedrive-for-cf7-wpforms-elementor-ninja-forms or similar) and check the main plugin PHP file header for the 'Version' field, or query it via wp-cli: wp plugin list --search='pipedrive' --format=json
    Affected if The installed version is 1.2.3 or lower (the vulnerability affects versions up to 1.2.3)
  2. Confirm Contact Form 7 is installed
    Check for the Contact Form 7 plugin in wp-content/plugins/ or query via wp-cli: wp plugin list --search='contact-form-7' --format=json
    Affected if Contact Form 7 is present alongside the vulnerable plugin (required for the POP chain to achieve file deletion)
  3. Verify the plugin is active
    Check plugin status via WordPress admin dashboard or wp-cli: wp plugin status pipedrive-for-cf7-wpforms-elementor-ninja-forms
    Affected if The plugin is active (the vulnerability is exploitable only on active plugins)
  4. Inspect the verify_field_val() function for unsafe deserialization
    Examine the plugin source code, specifically the verify_field_val() function, and look for unserialize() calls handling untrusted input without prior validation
    Affected if The code contains unserialize() on user-supplied input without sanitization (indicates the vulnerable code path exists)
  5. Check web server logs for exploitation attempts
    Review access logs for patterns containing serialized PHP objects in POST/GET parameters, particularly around the plugin's AJAX or form-handling endpoints
    Affected if Logs show requests with serialized object data or known POP chain indicators targeting the plugin endpoint

Your environment is affected if the Pipedrive integration plugin version is 1.2.3 or lower, the plugin is active, and Contact Form 7 is installed, allowing unauthenticated PHP object injection that can leverage the CF7 POP chain to delete files or achieve RCE.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 1.2.4 or later immediately. If immediate update is not possible, disable the plugin or implement WAF rules to block deserialization attack patterns at the web application layer.

Recommended fix Moderate confidence

Latest version newer than 1.2.3 (check WordPress plugin repository for version 1.2.4 or later)

  1. Check the current version of the 'Integration for Pipedrive and Contact Form 7, WPForms, Elementor, Ninja Forms' plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate the plugin and note the current version number
  4. If the installed version is 1.2.3 or earlier, update the plugin to the latest available version
  5. After updating, verify the plugin is running on a version newer than 1.2.3
  6. Consider reviewing user roles and permissions to limit exposure until the patch is applied
  7. If immediate update is not possible, consider disabling the plugin temporarily
Caveat Standard plugin update - review any settings changes after upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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