Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as donor-report (view-only) user
-
ExploitInvoke unchecked donor address-change handler
-
ImpactAdd, modify, or delete any donor's stored address
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated WordPress account that has been granted GiveWP donor-report (view) access but not donor-edit access, on a site running GiveWP before 4.19.0.1; the donor address-change handler performs no capability check. No special plugin configuration beyond the existence and assignment of that report-only capability is needed, and no user interaction is required. Exploitation is limited to the integrity of donor address data (add/modify/delete stored addresses) - there is no confidentiality or availability impact - and it is gated by the attacker already holding the report-level role, so it is primarily an insider / over-provisioned-user risk rather than an unauthenticated internet exposure. |
| Impact | This is a low-severity, low-priority issue despite being network-reachable. The input CVSS of 2.7 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N) reflects an authenticated flaw with only a low integrity impact and no confidentiality or availability impact, consistent with CWE-862 missing authorization. All exploitation signals agree on low urgency: EPSS is 0.13% (3rd percentile), there is no CISA KEV listing, and the vuln.today decision label is 'monitor'. A public PoC reference exists (WPScan) but it is not verified as working exploit code, so it should not be treated as confirmed active exploitation. One internal inconsistency is worth noting: the input vector uses PR:H, but the description indicates the actor is a lower-privilege user who holds only donor-report (view) access rather than an administrator - so PR:L is a more defensible privilege rating, which would not raise the score meaningfully. Net assessment: a genuine broken-access-control bug, but a monitor-and-patch item, not an emergency. |
| Exploit ScenarioDerived | A WordPress user who has been granted GiveWP donor-report (view) access - but deliberately not donor-edit rights - uses the donor address-change handler, which performs no capability check, to add, alter, or delete the stored address of any donor on the site. Because the vector is network-reachable with low complexity and no user interaction, the request can be issued directly once the actor holds the report-only role. A public PoC reference exists (WPScan) but is not verified as working exploit code. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 26, 2026
GiveWP before 4.19.0.1 allows authenticated users who hold donor-report (view) access, but not donor-edit access, to add, modify, or delete the stored address of any donor because the address-change handler lacks a capability check. This is a low-severity, low-priority issue despite being network-reachable, with EPSS at 0.13% (percentile 3%); a public PoC reference exists, but it is not verified as working exploit code.
RemediationAI
Upgrade GiveWP to 4.19.0.1 or later; vendor-released patch: 4.19.0.1. Until then, restrict donor-report (view) access to trusted accounts because that role is sufficient to exploit, and review donor address records for unexpected changes; removing report access from over-provisioned users removes the prerequisite at the cost of losing donor reporting for those users. Advisory: https://wpscan.com/vulnerability/9fae25ff-51e6-4137-83d6-e752374dae57/ and https://nvd.nist.gov/vuln/detail/CVE-2026-111981.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
GiveWP is a WordPress donation plugin, and the flaw is CWE-862 Missing Authorization: the donor address-change handler does not verify that the acting user has donor-edit capability, so a role granted only donor-report view can still mutate donor addresses. The trigger is described as handling donor address changes without a capability check; no memory-safety, injection, or remote code execution component is indicated. Authentication is required: the assessed CVSS vector uses PR:L and the exploitation conditions require an authenticated WordPress account with donor-report access but not donor-edit access. CPE data lists cpe:2.3:a:unknown:givewp:*:*:*:*:*:*:*:*.
Know when Givewp gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N
Actor holds only donor-report (view) access so PR:L not PR:H; network-reachable with no interaction (AV:N/AC:L/UI:N); only donor address integrity affected (I:L, C:N, A:N).
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
4DescriptionCVE.org
The GiveWP WordPress plugin before 4.19.0.1 does not perform a capability check when handling donor address changes, allowing users who have been granted donor-report (view) access but not donor-edit access to add, modify, or delete the stored address of any donor on the site.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all
The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all
Unauthenticated PHP object injection in the GiveWP WordPress donation plugin (all versions through 4.16.7.1) lets remote
Improper privilege management in the GiveWP WordPress donation plugin (affected ranging from 4.16.6 up to but not includ
GiveWP WordPress plugin before 4.16.3 exposes sensitive donor privacy data through an unauthenticated REST API endpoint
Stored cross-site scripting in the GiveWP WordPress plugin before version 4.16.3 allows authenticated users holding the
Stored cross-site scripting in GiveWP donation forms before 4.19.0.1 lets a user who already holds a custom GiveWP role
The Donations Widget plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 3.
The GiveWP WordPress plugin before 2.21.3 does not have CSRF in place when exporting data, and does not validate the exp
The GiveWP WordPress plugin before 2.17.3 does not escape the json parameter before outputting it back in an attribute i
The GiveWP - Donation Plugin and Fundraising Platform WordPress plugin before 2.10.0 was affected by a reflected Cross-S
The "Donation Plugin and Fundraising Platform" plugin before 2.3.1 for WordPress has wp-admin/edit.php csv XSS. Rated me
EUVD-2026-109346
GHSA-9wv6-rw6f-46c3
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB