dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-1916

HIGH · 7.5 CVSS v3.1 Published 2026-02-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 WPGSI: Spreadsheet Integration plugin for WordPress is vulnerable to unauthorized modification and loss of data due to missing capability checks and an insecure authentication mechanism on the `wpgsi_callBackFuncAccept` and `wpgsi_callBackFuncUpdate` REST API functions in all versions up to, and including, 3.8.3. Both REST endpoints use `permission_callback => '__return_true'`, allowing unauthenticated access. The plugin's custom token-based validation relies on a Base64-encoded JSON object containing the user ID and email address, but is not cryptographically signed. This makes it possible for unauthenticated attackers to forge tokens using publicly enumerable information (admin user ID and email) to create, modify, and delete arbitrary WordPress posts and pages, granted they know the administrator's email address and an active integration ID with remote updates enabled.

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 WPGSI plugin for WordPress has two REST API endpoints (`wpgsi_callBackFuncAccept` and `wpgsi_callBackFuncUpdate`) that use `permission_callback => '__return_true'`, allowing unauthenticated access. The custom token authentication relies on an unsigned Base64-encoded JSON object containing user ID and email, which can be forged by attackers who know the administrator's email and have an active integration ID with remote updates enabled. This enables unauthenticated attackers to create, modify, and delete arbitrary WordPress posts and pages.

MitigationUpdate the plugin to version 3.8.4 or later which implements proper capability checks and cryptographically signed token validation. Until patched, disable the plugin or restrict access to the vulnerable REST API endpoints via server-side configuration.

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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 WPGSI plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate WPGSI (or WP Google Sheets Importer). Record the version number displayed.
    Affected if Plugin is installed with version lower than 3.8.4 (the patched version)
  2. Test unauthenticated REST API access
    Send a GET request to /wp-json/wpgsi/v1/callback_accept and /wp-json/wpgsi/v1/callback_update without any authentication headers. Use curl or browser developer tools.
    Affected if Endpoints return any HTTP response other than 401 Unauthorized or 403 Forbidden, indicating the permission_callback is set to '__return_true'
  3. Verify vulnerable callback configuration in plugin code
    Access the plugin files via FTP or file manager. In the plugin directory, search for the REST route registration and verify that permission_callback is set to '__return_true' for the callback endpoints.
    Affected if permission_callback => '__return_true' is found in the endpoint registration for wpgsi_callBackFuncAccept or wpgsi_callBackFuncUpdate
  4. Check for active integrations with remote updates
    In WordPress admin, go to WPGSI plugin settings and look for any integration configurations. Check if remote updates or callback functionality is enabled for any integration ID.
    Affected if Any integration ID has remote updates or callback functionality enabled, providing the attacker with a valid integration ID for exploitation

The environment is affected if WPGSI plugin is active with a version below 3.8.4 and the vulnerable REST endpoints respond to unauthenticated requests while an integration with remote updates is enabled.

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 the plugin to version 3.8.4 or later which implements proper capability checks and cryptographically signed token validation. Until patched, disable the plugin or restrict access to the vulnerable REST API endpoints via server-side configuration.

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-2026-1916 — 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-2026-1916 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