CVE-2026-11981

GiveWP <= 4.15.3 - Cross-Site Request Forgery

2026-06-30 16:29
javitoia

Strategic Overview

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

At a glance

CVE-2026-11981 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the GiveWP WordPress plugin, affecting versions <= 4.15.3. 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 4.15.4; sites on affected versions should update now. Disclosed June 2026, reported by javitoia.

Vulnerability Overview

The GiveWP plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 4.15.3 This is due to missing nonce validation on the give_set_notification_status_handler() function. This makes it possible for unauthenticated attackers to disable donation email notifications 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.

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

GiveWP <= 4.15.3 carries this weakness at give_set_notification_status_handler(), 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 4.15.4: builds <= 4.15.3 are affected, anything from 4.15.4 onward is not.

Remediation

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-11981https://www.wordfence.com/threat-intel/vulnerabilities/id/49954c72-df0d-46ec-a252-8af84dea41bfhttps://nvd.nist.gov/vuln/detail/CVE-2026-11981

Related records

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