CVE-2025-67979
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 · uneditedImproper Control of Generation of Code ('Code Injection') vulnerability in WesternDeal WPForms Google Sheet Connector gsheetconnector-wpforms allows Code Injection.This issue affects WPForms Google Sheet Connector: from n/a through <= 4.0.1.
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 · low confidenceA code injection vulnerability in the WesternDeal WPForms Google Sheet Connector WordPress plugin (versions <=4.0.1) allows attackers to inject and execute arbitrary code, likely through improper input validation in plugin parameters that connect forms to Google Sheets.
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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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.
-
Verify WPForms Google Sheet Connector plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'WPForms Google Sheet Connector' or 'WesternDeal WPForms Google Sheet Connector' in the list of active or inactive plugins.Affected if The plugin is present in the plugins list regardless of activation status
-
Determine the installed plugin versionIn the Plugins page, click on the plugin name to view its details, or inspect the plugin header in /wp-content/plugins/ folder for the version number. Compare against the affected range: versions 4.0.1 and below.Affected if The displayed version number is 4.0.1 or lower
-
Confirm Google Sheets integration is configuredGo to WPForms > Settings > Google Sheets (or Integrations depending on plugin structure). Check if any form is connected to a Google Sheet by viewing the connection status for each form.Affected if At least one form has an active Google Sheets connection configured with an email/API key and selected spreadsheet
-
Inspect plugin settings for suspicious entriesReview all plugin settings pages for unexpected or encoded values in fields such as API credentials, spreadsheet IDs, or sheet names. Look for unusual characters, base64-encoded strings, or shell commands.Affected if Any field contains code-like characters, encoded strings, or unexpected command syntax that was not entered by an administrator
User is affected if the plugin is installed with version 4.0.1 or lower AND has Google Sheets integration enabled with any configured form.
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.
From vendor dataUpdate the WPForms Google Sheet Connector plugin to a version beyond 4.0.1 once available, or implement input sanitization/validation fixes at the application layer to prevent malicious code injection.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67979 — 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-67979 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