CVE-2026-1916
Unauthenticated REST API Access in WPGSI Plugin Enables Data Modification
Publication date: 2026-02-25
Last updated on: 2026-02-25
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordfence | wpgsi | to 3.8.3 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-862 | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The WPGSI: Spreadsheet Integration plugin for WordPress has a vulnerability in its REST API functions `wpgsi_callBackFuncAccept` and `wpgsi_callBackFuncUpdate` in all versions up to and including 3.8.3. These endpoints use a permission callback that always returns true, allowing unauthenticated access.
The plugin uses a custom token-based validation that relies on a Base64-encoded JSON object containing the user ID and email address, but this token is not cryptographically signed. Because of this, attackers who know the administrator's email and an active integration ID with remote updates enabled can forge tokens.
This allows unauthenticated attackers to create, modify, and delete arbitrary WordPress posts and pages by exploiting the insecure authentication mechanism and missing capability checks.
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized modification and loss of data on your WordPress site. Specifically, attackers can create, modify, or delete posts and pages without authentication.
Since the REST API endpoints do not properly verify permissions and rely on an insecure token mechanism, attackers who know certain publicly enumerable information (like the admin's email and integration ID) can exploit this to compromise site content.
The impact includes potential defacement, data corruption, or loss of important content, which can disrupt your website's operation and damage your reputation.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This vulnerability involves unauthorized access to the WordPress REST API endpoints `wpgsi_callBackFuncAccept` and `wpgsi_callBackFuncUpdate` due to missing capability checks and insecure token validation.'}, {'type': 'paragraph', 'content': 'To detect exploitation attempts on your network or system, you can monitor HTTP requests to these REST API endpoints for suspicious activity such as unauthenticated POST or GET requests containing tokens or payloads.'}, {'type': 'list_item', 'content': 'Use web server access logs to search for requests to `/wp-json/wpgsi/accept` or `/wp-json/wpgsi/update` endpoints.'}, {'type': 'list_item', 'content': 'Example command to check Apache or Nginx logs for such requests: `grep -E "/wp-json/wpgsi/(accept|update)" /var/log/apache2/access.log`'}, {'type': 'list_item', 'content': 'Look for requests with unusual or missing authentication tokens or malformed tokens in the request parameters or headers.'}, {'type': 'list_item', 'content': 'Monitor for HTTP 401 Unauthorized responses or 400 Bad Request responses related to these endpoints, which may indicate attempts to exploit the token validation.'}, {'type': 'list_item', 'content': 'Use network monitoring tools or intrusion detection systems (IDS) to alert on REST API calls to these endpoints from unauthenticated sources.'}] [2, 3, 4]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the WPGSI: Spreadsheet Integration plugin to version 3.8.4 or later, which implements strict token-based authentication with HMAC-SHA256 signature verification and proper permission callbacks.
If updating immediately is not possible, consider disabling or restricting access to the vulnerable REST API endpoints `/wp-json/wpgsi/accept` and `/wp-json/wpgsi/update` via web server configuration or firewall rules to prevent unauthenticated access.
- Update the plugin to version 3.8.4 or newer where the permission callback is changed from `__return_true` to a secure `wpgsi_permission_check` enforcing token validation.
- Restrict access to the REST API endpoints by IP address or authentication at the web server or application firewall level.
- Monitor logs for suspicious activity targeting these endpoints and respond accordingly.
- Ensure administrator email addresses and integration IDs are kept confidential to reduce the risk of token forgery.