Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify donor e-mail linked to admin
-
DeliverySubmit non-normalised e-mail variant
-
ExploitPlugin resolves attacker as target donor
-
ExecutionTrigger password-set on linked account
-
PersistLog in as administrator
-
ImpactFull site compromise
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Least privilege enforcement
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 | Exploitation requires a target donor record whose e-mail is linked to a WordPress user account - ideally an administrator - within GiveWP before 4.16.8.1 (affected 4.16.6 onward). The attacker must supply an e-mail string that differs from the stored value yet resolves to it under the plugin's inconsistent normalisation (e.g. case, surrounding whitespace, or alias/dot variations), which is the AC:H barrier. No authentication (PR:N) and no user interaction (UI:N) are needed. The practical limiter is knowledge of a valid donor e-mail that maps to a privileged account plus discovery of the exact normalisation-mismatch input; a public WPScan exploit reduces the difficulty of constructing that input. |
| Impact | This is a genuine high-priority issue despite modest exploitation-probability signals. The CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, base 8.1) describes an unauthenticated, network-reachable flaw with full C/I/A impact - the ability to reset an administrator's WordPress password equals complete site takeover. The AC:H metric is the sole meaningful brake: the attacker must craft an e-mail value that is treated as equivalent on lookup but differs from the normalised stored form, and must target a donor record linked to a privileged account. Countervailing signals are mixed: EPSS is low at 0.18% (8th percentile), and the CVE is NOT on CISA KEV, so there is no evidence of active mass exploitation. However, a public exploit exists (WPScan), which materially raises real-world risk versus a theoretical bug. The low EPSS against a public POC plus admin-takeover impact suggests exploitation is feasible but not yet widespread/automated - consistent with an emerging rather than commodity threat. Net: treat as urgent patch priority for any GiveWP-running site, weighting impact and POC availability over the currently-low EPSS. |
| Exploit ScenarioDerived | An unauthenticated attacker identifies (or registers) a donor e-mail that maps to a privileged WordPress user, then submits a non-normalised variant of that address (e.g. differing case, whitespace, or dot/alias formatting) so the plugin's lookup resolves them as that donor. Because a public exploit is available (WPScan), the attacker uses it to trigger the password-set flow and assign a new WordPress password to the administrator account linked to the donor, then logs in with full admin control. The AC:H rating reflects that the attacker must know or discover a donor-to-admin linkage and craft the exact normalisation-mismatch string. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 17, 2026
Improper privilege management in the GiveWP WordPress donation plugin (affected ranging from 4.16.6 up to but not including 4.16.8.1) lets unauthenticated remote attackers be mis-resolved as an arbitrary donor and then set the WordPress account password of any user linked to that donor record, up to and including an administrator. The root cause is CWE-269: the plugin does not consistently normalise donor e-mail addresses between the value it stores and the value it later uses for donor lookup, so a crafted e-mail string (case, whitespace, or alias/dot variations) can collide with a privileged donor identity. Exploitation is confirmed feasible - publicly available exploit code exists via WPScan and no authentication or user interaction is required - although the AC:H factor and low EPSS (0.18%, 8th percentile) indicate a targeted rather than mass-exploitation profile; there is no CISA KEV entry, so active exploitation is not confirmed. Vendor-released patch: 4.16.8.1.
RemediationAI
Vendor-released patch: 4.16.8.1 - upgrade the GiveWP plugin to 4.16.8.1 or later immediately, and verify the installed version after updating that cached or manually staged copies have not been left behind (see the WPScan advisory at https://wpscan.com/vulnerability/83fcea02-345a-443c-b14e-316533a2fd7d/). Because exploitation permits password resets against donor-linked accounts, treat any site running an affected version as potentially compromised: force password resets for all administrator accounts and for every WordPress user linked to a GiveWP donor, review wp_users and GiveWP donor records for unexpected account linkages or e-mail mismatches, and inspect logs for anomalous password-change or donor-lookup requests. Where the plugin cannot be patched immediately, disable the GiveWP donor-account / WordPress user registration linkage so donor records no longer resolve to native accounts - the trade-off is that donor self-service portal features and donor history become unavailable - or temporarily deactivate GiveWP if donation processing is non-critical, accepting loss of donation intake and reporting. Additional compensating controls include restricting or blocking access to the GiveWP front-end routes and REST/AJAX endpoints used by the donor password flow at the WAF or reverse proxy (which may also break legitimate donor sign-up flows and must be scoped carefully), and enforcing strong, unique administrator credentials plus monitoring for unauthorised password changes. No public KEV listing exists, so emergency out-of-band response is at the operator's discretion, but the presence of publicly available exploit code and the administrator-takeover impact justify rapid patching.
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 widely deployed WordPress donation and fundraising plugin that maintains donor records and can link a donor to a native WordPress user account. The defect is an identity-resolution flaw in the CWE-269 (Improper Privilege Management) class: the e-mail string written to the donor record is not canonicalised the same way as the string used when the plugin performs a donor lookup. Because the stored and lookup representations can diverge (mixed case, leading/trailing whitespace, or dot/alias permutations that resolve to the same mailbox), an unauthenticated request can be matched to a donor whose e-mail an attacker supplies in an alternate but semantically equivalent form. Once the plugin resolves the request to that donor, the caller inherits the donor's linked WordPress identity via the password-setting workflow, yielding account takeover of any user associated with that donor - including an administrator. The CVSS:3.1 vector AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H encodes the network reachability and absence of authentication or user interaction, with AC:H reflecting the requirement to know a valid donor e-mail that maps to a privileged account and to construct the exact normalisation-mismatch input; the public WPScan exploit reduces that construction effort. The CPE string cpe:2.3:a:unknown:givewp:*:*:*:*:*:*:*:* is vendor-unpopulated but correctly scopes the affected component to GiveWP; EUVD-2026-80196 records the affected range as 4.16.6 < 4.16.8.1.
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:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Unauthenticated network flaw (PR:N/AV:N) but requires crafting a normalisation-mismatch e-mail tied to a privileged donor (AC:H); admin takeover yields full C/I/A.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
4DescriptionCVE.org
The GiveWP WordPress plugin before 4.16.8.1 does not consistently normalise a donor's e-mail address between the value it stores and the value it later uses to look that donor up, allowing unauthenticated users to be resolved as an arbitrary donor and to set the WordPress password of any user account linked to one, including an administrator's.
Technical POC Analysis
Evidence caveat up front: the supplied evidence is the WPScan advisory entry, CVE metadata, and CVSS/CWE classification only.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
The GiveWP WordPress donation plugin (versions 4.16.6 to 4.16.8.1) contains a privilege management flaw that allows attackers to reset passwords for any user linked to a donor record, including administrators, risking full site takeover. Publicly available exploit code exists, and while no active exploitation is confirmed, organizations running the plugin face significant reputational and operational risk due to potential compromise of donor data and website integrity. Leadership should prioritize immediate patching to protect sensitive donation information and maintain stakeholder trust.
Apply vendor patch.
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
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
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
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
Path traversal in the GiveWP WordPress plugin before 4.19.0.1 allows an authenticated user holding a high-privilege Give
EUVD-2026-80196
GHSA-f8r4-h4wf-5gg7
NVD
CVE.org
EPSS
Exploit-DB