dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-67570

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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
Missing Authorization vulnerability in WesternDeal WPForms Google Sheet Connector gsheetconnector-wpforms allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WPForms Google Sheet Connector: from n/a through <= 4.0.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 · moderate confidence

Missing authorization vulnerability in the WPForms Google Sheet Connector plugin (gsheetconnector-wpforms) allows authenticated users to exploit incorrectly configured access control security levels, potentially enabling unauthorized access to sensitive functions or data that should require higher privileges.

MitigationImplement proper capability checks and authorization validation on all sensitive functions within the plugin; update to version 4.0.1 or later once available.

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

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. Verify the WPForms Google Sheet Connector plugin is installed
    Navigate to WordPress admin > Plugins and confirm gsheetconnector-wpforms appears in the installed plugins list, or query the database wp_options table for option_name containing 'active_plugins'
    Affected if The plugin gsheetconnector-wpforms is present in the WordPress installation
  2. Determine the installed version of the plugin
    In WordPress admin > Plugins, find the WPForms Google Sheet Connector entry and read the version number from the plugin description; alternatively, inspect the plugin main file header in wp-content/plugins/gsheetconnector-wpforms/ for the 'Version' tag
    Affected if The installed version is lower than 4.0.1 (the fixed version)
  3. Confirm the plugin integration is active
    Check WPForms > Settings (or the plugin's own settings page) to see if the Google Sheets integration is enabled and connected to a Google account
    Affected if The Google Sheet Connector integration is configured and active, exposing the affected functionality
  4. Test for privilege escalation via sensitive functions
    Using a lower-privileged user account (subscriber or contributor role), attempt to access plugin admin pages or trigger actions that should require administrator privileges; observe whether unauthorized access is permitted
    Affected if Lower-privileged authenticated users can access functions or data that should require administrator-level capabilities

The environment is affected if the WPForms Google Sheet Connector plugin (gsheetconnector-wpforms) is installed with a version before 4.0.1 and the Google Sheets integration is active, allowing lower-privileged users to access privileged functions.

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

Implement proper capability checks and authorization validation on all sensitive functions within the plugin; update to version 4.0.1 or later once available.

Recommended fix Moderate confidence

4.0.1 or latest available version

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'WPForms Google Sheet Connector' (gsheetconnector-wpforms) plugin
  4. 4. Check the current installed version number
  5. 5. Look for an available update for this plugin in the Plugins list or check the WordPress plugin repository for the latest version
  6. 6. If a newer version is available (likely 4.0.1 or higher), update the plugin to the latest version

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
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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