CVE-2026-11981
Deferred Deferred - Pending Action

Cross-Site Request Forgery in GiveWP WordPress Plugin

Vulnerability report for CVE-2026-11981, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-01

Last updated on: 2026-07-01

Assigner: Wordfence

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-01
Last Modified
2026-07-01
Generated
2026-07-21
AI Q&A
2026-07-01
EPSS Evaluated
2026-07-20
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
givewp givewp to 4.15.3 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-352 The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

The GiveWP plugin for WordPress has a vulnerability known as Cross-Site Request Forgery (CSRF) in versions up to and including 4.15.3. This occurs because the function give_set_notification_status_handler() lacks nonce validation, which is a security measure to verify legitimate requests.

As a result, an attacker who is not authenticated can trick a site administrator into performing an unintended action, such as clicking on a malicious link, which then disables donation email notifications on the site.

Detection Guidance

This vulnerability affects the GiveWP WordPress plugin versions up to and including 4.15.3 due to missing nonce validation in the give_set_notification_status_handler() function. Detection involves identifying if the vulnerable plugin version is installed on your WordPress site.

To detect the presence of the vulnerable GiveWP plugin version on your system, you can check the plugin version via the WordPress admin dashboard or by inspecting the plugin files directly.

From the command line, you can use the following commands to check the installed GiveWP plugin version:

  • Navigate to the WordPress plugins directory, usually wp-content/plugins/givewp, and open the main plugin file (e.g., givewp.php) to check the version header.
  • Run a command like: grep 'Version:' wp-content/plugins/givewp/givewp.php
  • Alternatively, use WP-CLI to check the plugin version: wp plugin list --status=active | grep givewp

Network detection of exploitation attempts is challenging because the attack requires tricking an administrator into clicking a forged request. Monitoring for unusual POST requests to endpoints related to notification status changes in the GiveWP plugin may help.

Impact Analysis

This vulnerability allows unauthenticated attackers to disable donation email notifications by tricking an administrator into clicking a malicious link. This can lead to missed notifications about donations, potentially affecting the site's ability to track or respond to donations properly.

While it does not directly compromise data confidentiality or availability, it impacts the integrity of the notification process, which could disrupt communication and operational workflows related to donations.

Mitigation Strategies

The vulnerability exists in GiveWP plugin versions up to and including 4.15.3 due to missing nonce validation in the give_set_notification_status_handler() function.

To mitigate this vulnerability, immediately update the GiveWP plugin to a version later than 4.15.3 where the issue is fixed.

Additionally, ensure that site administrators are cautious about clicking on suspicious links that could trigger forged requests.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-11981. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart