CVE-2025-7697
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 · uneditedThe Integration for Google Sheets 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.1.1 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 confidenceThe plugin is vulnerable to PHP Object Injection through unsafe deserialization in the verify_field_val() function. Unauthenticated attackers can inject arbitrary PHP objects, and when combined with a POP chain in Contact Form 7, can delete arbitrary files including wp-config.php, leading to denial of service or remote code execution.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the affected pluginLocate the WordPress plugin associated with this CVE in your wp-content/plugins directory and note its name for version checkingAffected if the plugin is present in the environment
-
Check the plugin versionInspect the main plugin file (typically plugin-name.php) or the plugin header in wp-admin to find the installed version numberAffected if the installed version is lower than 1.1.2 (versions before 1.1.2 are vulnerable)
-
Verify Contact Form 7 presenceCheck if the Contact Form 7 plugin is installed in the WordPress environment, as the POP chain requires itAffected if Contact Form 7 is installed and provides the gadget chain for object injection exploitation
-
Confirm plugin is activeCheck the wp_options table for active_plugins or inspect the plugins list in WordPress adminAffected if the vulnerable plugin is activated and publicly accessible
-
Check for unauthorized access indicatorsReview web server logs and WordPress audit logs for unusual deserialization calls or attempts targeting the verify_field_val functionAffected if unauthorized requests to the vulnerable function are found in logs
You are affected if the plugin version is below 1.1.2 AND Contact Form 7 is installed, allowing unauthenticated PHP object injection via the verify_field_val function
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 · scopedUpdate the plugin to version 1.1.2 or later immediately, as this is an unauthenticated critical vulnerability. Also ensure Contact Form 7 is updated to patch the POP chain.
Upgrade to version 1.1.2 or later (the latest available version)
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the 'Integration for Google Sheets and Contact Form 7, WPForms, Elementor, Ninja Forms' plugin
- If an update is available, click 'Update Now' to update the plugin to the latest version
- Alternatively, manually download the latest version from wordpress.org and upload via Plugins > Add New > Upload Plugin
- After updating, verify the plugin is running version 1.1.2 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7697 — 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-7697 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