GiveWP <= 2.25.1 - Cross-Site Request Forgery via save

2023-03-08 00:00
Anonymous

Strategic Overview

Status
Patched in 2.25.2
Affected Plugin
GiveWP – Donation Plugin and Fundraising Platform
Affected Version
<= 2.25.1
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE pending
View all GiveWP – Donation Plugin and Fundraising Platform vulnerabilities

At a glance

This record tracks a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the GiveWP WordPress plugin, affecting versions <= 2.25.1. 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 2.25.2; sites on affected versions should update now. Disclosed March 2023.

Vulnerability Overview

The GiveWP plugin is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.25.1. This is due to missing or incorrect nonce validation on the 'save' AJAX function. This makes it possible for unauthenticated attackers to import donations via forged request granted a CSV file containing those donations has been uploaded and 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)

GiveWP <= 2.25.1 carries this weakness at save, 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 GiveWP the fix is 2.25.2: builds <= 2.25.1 are affected, anything from 2.25.2 onward is not.

Remediation

Update to version 2.25.2, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to GiveWP: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: GiveWP 2.25.2 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/cb7ec7ad-797b-4a5c-9b1c-31284083faef

Related records

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