# CVE-2026-1916: Missing authorization in WPGSI: Spreadsheet Integration

> Unauthenticated attackers can create, modify, or delete arbitrary posts by forging unsigned Base64 tokens if they know the admin email and an active integration ID.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Feb 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-v72r-wpp2-8369

## What is CVE-2026-1916?

CVE-2026-1916 is a high-severity missing authorization vulnerability in javmah WPGSI: Spreadsheet Integration, published on 25 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-1916?


## How do I fix CVE-2026-1916?

No fix has been published for CVE-2026-1916 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-1916 being exploited?

There is no known exploitation of CVE-2026-1916 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-1916 and fix it if it is affected.

What it is: CVE-2026-1916 is a high-severity missing authorization vulnerability in javmah WPGSI: Spreadsheet Integration, published on 25 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-1916 in the wild and no public exploit code.

Affected product: javmah WPGSI: Spreadsheet Integration. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-1916/ (Markdown: https://insights.sbomify.com/CVE-2026-1916/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-1916
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-1916
- OSV: https://osv.dev/vulnerability/CVE-2026-1916

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-1916/
Summaries are generated and may contain mistakes; the official description above is the record.