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.
CVE-2026-11981
MEDIUMPre-NVD 4.34.3—Trending — 4 sources updated this week
EchelonGraph scoreHIGH confidence
Score 4.3 from GitHub Security Advisory published 2026-07-01. a secondary CVSS source baseline 4.3; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
4.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.3Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.3
- EG Score
- 4.3(high)
- EPSS
- 4.9%
- KEV
- Not listed
Published
July 1, 2026
Last Modified
July 1, 2026
References (9)
- security@wordfencehttps://plugins.trac.wordpress.org/browser/give/tags/3.19.4/includes/admin/emails/ajax-handler.php#L24
- security@wordfencehttps://plugins.trac.wordpress.org/browser/give/tags/3.19.4/includes/admin/emails/ajax-handler.php#L25
- security@wordfencehttps://plugins.trac.wordpress.org/browser/give/tags/3.19.4/includes/admin/emails/ajax-handler.php#L32
- security@wordfencehttps://plugins.trac.wordpress.org/browser/give/tags/4.15.3/includes/admin/emails/ajax-handler.php#L24
- security@wordfencehttps://plugins.trac.wordpress.org/browser/give/tags/4.15.3/includes/admin/emails/ajax-handler.php#L25
- security@wordfencehttps://plugins.trac.wordpress.org/browser/give/tags/4.15.3/includes/admin/emails/ajax-handler.php#L32
- security@wordfencehttps://plugins.trac.wordpress.org/changeset/3573301/give/trunk/includes/admin/emails/ajax-handler.php
- security@wordfencehttps://plugins.trac.wordpress.org/changeset?old_path=%2Fgive/tags/4.15.3&new_path=%2Fgive/tags/4.15.4
- security@wordfencehttps://www.wordfence.com/threat-intel/vulnerabilities/id/49954c72-df0d-46ec-a252-8af84dea41bf?source=cve
Vendor Advisories for CVE-2026-11981(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 19× in last 7d / 19× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 12:54 UTCEG score recompute
- 2026-07-06 12:54 UTCGHSA enrichment
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 11:22 UTCEG score recompute
- 2026-07-05 11:22 UTCGHSA enrichment
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 09:52 UTCEG score recompute
- 2026-07-04 09:52 UTCGHSA enrichment
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 08:22 UTCEG score recompute
- 2026-07-03 08:22 UTCGHSA enrichment
- 2026-07-02 06:52 UTCEG score recompute
- 2026-07-02 06:52 UTCGHSA enrichment
- 2026-07-01 15:06 UTCEPSS rescore
- 2026-07-01 15:06 UTCEPSS rescore
- 2026-07-01 05:22 UTCEG score recompute
- 2026-07-01 05:20 UTCNVD updatefirst tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-11981?
CVE-2026-11981 is a medium vulnerability published on July 1, 2026. 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 givesetnotificationstatushandler() function. This makes it possible for unauthenticated attackers to disable donation email…
When was CVE-2026-11981 disclosed?
CVE-2026-11981 was first published in the National Vulnerability Database on July 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-11981 actively exploited?
CVE-2026-11981 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-11981?
CVE-2026-11981 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-11981?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-11981, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-11981
Is Your Infrastructure Affected by CVE-2026-11981?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.