Spreadsheet Integration <= 3.8.2 - Cross-Site Request Forgery to Arbitrary Post Publish
Strategic Overview
- Status
- Patched in 3.8.3
- Affected Plugin
- WPGSI: Spreadsheet Integration
- Affected Version
<= 3.8.2- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2025-1463
At a glance
CVE-2025-1463 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WPGSI WordPress plugin, affecting versions <= 3.8.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.8.3; sites on affected versions should update now. Disclosed March 2025, reported by Krzysztof Zając.
Vulnerability Overview
The Spreadsheet Integration plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.8.2. This is due to improper nonce validation within the class-wpgsi-show.php script. This makes it possible for unauthenticated attackers to publish arbitrary posts, including private, granted they can trick a site administrator into performing an action such as clicking on a link.
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.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in WPGSI <= 3.8.2 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For WPGSI the fix is 3.8.3: builds <= 3.8.2 are affected, anything from 3.8.3 onward is not.
Remediation
Update to version 3.8.3, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WPGSI: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WPGSI 3.8.3 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in WPGSI: Spreadsheet Integration
- 7.5CVE-2026-1916: WPGSI Unauthenticated Arbitrary Post Creation
CVE-2026-1916 - 6.3CVE-2024-6590: Spreadsheet Integration Authenticated (Subscriber+)
CVE-2024-6590 - 6.3CVE-2022-4974: Freemius SDK <= 2.4.2 Missing Authorization Checks
CVE-2022-4974 - 6.1CVE-2023-33999: Freemius SDK <= 2.5.9 Reflected Cross-Site Scripting
CVE-2023-33999 - 6.1Spreadsheet Integration and Spreadsheet Integration Pro Reflected XSS
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C