Spreadsheet Integration and Spreadsheet Integration Pro <= 3.5.0 - Cross-Site Request Forgery

2021-12-24 00:00
WPScanTeam

Strategic Overview

Status
Patched in 3.6.0
Affected Plugin
WPGSI: Spreadsheet Integration
Affected Version
<= 3.5.0
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE pending
View all WPGSI: Spreadsheet Integration vulnerabilities

At a glance

This record tracks a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the WPGSI WordPress plugin, affecting versions <= 3.5.0. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.6.0; sites on affected versions should update now. Disclosed December 2021, reported by WPScanTeam.

Vulnerability Overview

The Spreadsheet Integration and Spreadsheet Integration Professional plugins for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.5.0. This is due to missing or incorrect nonce validation on the 'wpgsi_WorksheetColumnsTitle' function. This makes it possible for unauthenticated attackers to access otherwise restricted admin actions via a forged request 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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-352: Cross-Site Request Forgery (CSRF)

WPGSI <= 3.5.0 carries this weakness at wpgsi_WorksheetColumnsTitle, and reaching it 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.6.0: builds <= 3.5.0 are affected, anything from 3.6.0 onward is not.

Remediation

Update to version 3.6.0, 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.6.0 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/6a3dddda-3a65-42b6-9dc8-760bc3a24dcf

Related records

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