dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-22686

MEDIUM · 5.3 CVSS v3.1 Published 2025-02-03
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 CF7 Google Sheets Connector cf7-google-sheets-connector allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects CF7 Google Sheets Connector: from n/a through <= 5.0.17.

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 CF7 Google Sheets Connector WordPress plugin allows attackers to bypass access control checks due to incorrectly configured security levels, potentially enabling unauthorized access to plugin functionality or data.

MitigationUpdate to a patched version of the plugin (greater than 5.0.17) that properly enforces authorization checks, or if no patch exists, implement additional access controls at the web server/application level to restrict unauthorized access to plugin endpoints.

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. Confirm CF7 Google Sheets Connector plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'CF7 Google Sheets Connector' or check the plugin files in wp-content/plugins/cf7-google-sheets-connector for existence
    Affected if The plugin is installed and active in WordPress
  2. Identify installed plugin version
    In WordPress admin Plugins list, find CF7 Google Sheets Connector and note the version number displayed under the plugin name, or open the main plugin PHP file and look for the 'Version:' header in the plugin comments
    Affected if Version is 5.0.17 or lower (the vulnerable version range)
  3. Verify plugin endpoints are network-accessible
    Check if the plugin exposes any REST API routes or admin-ajax.php actions by reviewing the plugin code for register_rest_route or do_action calls, then attempt to access these endpoints without authentication from an external host
    Affected if Plugin endpoints respond to unauthenticated requests, indicating the authorization bypass is exploitable
  4. Confirm Google Sheets integration is configured
    In WordPress admin, navigate to the CF7 Google Sheets Connector settings page and verify if a Google API key or service account credentials are configured and saved
    Affected if The plugin is configured with valid Google credentials, making the unauthorized access to data more impactful

If the plugin is installed, version 5.0.17 or lower, and its endpoints are accessible without authentication, the environment is likely affected by this authorization bypass vulnerability.

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 (greater than 5.0.17) that properly enforces authorization checks, or if no patch exists, implement additional access controls at the web server/application level to restrict unauthorized access to plugin endpoints.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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