CVE-2026-1916

WPGSI: Spreadsheet Integration <= 3.8.3 - Missing Authorization to Unauthenticated Arbitrary Post Creation and Deletion via Forged Base64 Token

Strategic Overview

Status
Patched in 3.8.4
Affected Version
<= 3.8.3
CVSS
7.5High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-1916
View all WPGSI: Spreadsheet Integration vulnerabilities

At a glance

CVE-2026-1916 is a high-severity Missing Authorization vulnerability in the WPGSI WordPress plugin, affecting versions <= 3.8.3. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 3.8.4; sites on affected versions should update now. Disclosed February 2026, reported by Osvaldo Noe Gonzalez Del Rio (Os).

Vulnerability Overview

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 Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on integrity.

CWE-862: Missing Authorization

WPGSI <= 3.8.3 carries this weakness at __return_true, and reaching it takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For WPGSI the fix is 3.8.4: builds <= 3.8.3 are affected, anything from 3.8.4 onward is not.

Remediation

Update to version 3.8.4, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: WPGSI 3.8.4 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C