Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach WordPress site running GiveWP
-
DeliverySend crafted request to vulnerable endpoint
-
ExploitSatisfy complex precondition for privilege flaw
-
ExecutionTrigger incorrect privilege assignment
-
PersistGain elevated/administrative privileges
-
ImpactCompromise site data and integrity
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Privilege assignment review
|
| Exploitation Conditions | Exploitation requires network access to a WordPress installation with the GiveWP plugin at version 4.17.0 or earlier; no authentication (PR:N) and no user interaction (UI:N) are needed. The primary limiting factor is the High attack complexity (AC:H): the advisory's CVSS vector indicates success depends on conditions the attacker cannot fully control - the specific feature, request sequence, or state that triggers the incorrect privilege assignment is not detailed in the available data, so the exact precondition should be verified against the Patchstack advisory. Sites not running GiveWP, or already updated past 4.17.0, are not affected. |
| Impact | This is a genuinely serious issue by CVSS (8.1 High) but with important mitigating nuance. The vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N) describes a network-reachable, fully unauthenticated privilege escalation with complete confidentiality, integrity, and availability impact (C:H/I:H/A:H) - an attacker needs no credentials and no user interaction, which is the worst-case access profile. The key tempering signal is AC:H (High attack complexity), meaning successful exploitation depends on conditions outside the attacker's control (e.g., a race, specific state, or non-trivial preconditions), which lowers the practical exploitation rate relative to an AC:L bug of the same impact. No EPSS score, no CISA KEV listing, and no public proof-of-concept were provided in the intelligence, so there is no evidence of active exploitation or mass scanning at this time; the risk is currently theoretical-but-credible rather than confirmed-and-widespread. Because the only source is a single Patchstack advisory with no corroborating vendor advisory or NVD CPE version detail beyond '<=4.17.0', treat the version boundary and the precise exploitation mechanism as not independently verified. Net: prioritize patching given unauthenticated network reach on a popular plugin, but the AC:H gate and absence of exploitation signals argue against emergency-incident treatment. |
| Exploit ScenarioDerived | A remote, unauthenticated attacker targets a WordPress site running the GiveWP donation plugin at version 4.17.0 or earlier and sends crafted requests that exploit an incorrect privilege-assignment flaw (CWE-266) to elevate their effective privileges. Because the flaw is AC:H, the attacker must satisfy specific preconditions or win a timing/state condition before the escalation succeeds. No public exploit code was identified at time of analysis, so exploitation would currently require independent development. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 06, 2026
Unauthenticated privilege escalation in the GiveWP WordPress donation plugin (versions up to and including 4.17.0) lets a remote attacker gain elevated privileges on a vulnerable site without any credentials or user interaction, consistent with the assessed vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. The key mitigating nuance is the High attack complexity: success depends on preconditions the attacker cannot fully control, so this is a serious 8.1 High-severity issue rather than a trivially scriptable one. No public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV, but because it is unauthenticated and grants high confidentiality, integrity, and availability impact, sites running GiveWP 4.17.0 or earlier should treat it as urgent; sites that do not run the plugin or have already moved past 4.17.0 are not affected.
RemediationAI
The provided data does not identify an exact fixed version - the affected range is stated only as GiveWP <=4.17.0 - so the primary action is to update the plugin to the latest available release above that line and confirm the fixed version against the vendor/Patchstack advisory at https://patchstack.com/database/wordpress/plugin/give/vulnerability/wordpress-givewp-plugin-4-17-0-privilege-escalation-vulnerability?_s_id=cve; do not assume an earlier or unrelated build is safe without checking. If an immediate upgrade is not possible, deploy compensating controls that target the privilege-assignment path: enforce a WAF rule set that blocks or challenges anomalous unauthenticated POST and AJAX/REST requests to GiveWP endpoints, temporarily disable non-essential donation and registration-related plugin functionality (trade-off: loss of fundraising and front-end form availability), and restrict administrative access to /wp-admin and the WordPress REST API by IP allowlist or basic authentication where operationally feasible (trade-off: breaks legitimate remote administration and integrations). Layer on continuous monitoring for unexpected role or capability changes - alert on new administrator accounts, modified wp_capabilities entries, and unfamiliar plugins - and validate that WordPress application passwords, salts, and all admin credentials are rotated if suspicious activity is observed. Given the High attack complexity, these measures materially raise the bar even though they do not eliminate the flaw; note that any protection is a stopgap and only the vendor patch fully resolves CWE-266 in GiveWP.
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 fundraising/donation plugin, packaged through the WordPress plugin ecosystem and tracked here under the CPE vendor 'nexcess' (cpe:2.3:a:nexcess:givewp:*:*:*:*:*:*:*:*). The root cause class is CWE-266, Incorrect Privilege Assignment, meaning the plugin assigns a privilege level or role to an actor that should not receive it - for example a request handler, registration/setup flow, or AJAX/REST endpoint that elevates a user or performs a privileged action without correctly verifying who is making the request or what role they should hold. The unauthenticated rating (PR:N) combined with network reachability (AV:N) means the flaw is exposed through the plugin's web-facing surface and does not require a pre-existing account or victim interaction (UI:N), while the High attack complexity (AC:H) indicates exploitation hinges on an additional state, feature configuration, or request sequence that the advisory does not detail in the available data. The underlying PHP/WordPress role-and-capability model is the mechanism abused: because WordPress capabilities gate administrative actions, an incorrect privilege assignment can cascade into broader site compromise. The CVSS scope is unchanged (S:U), so impact is confined to the vulnerable WordPress component's security authority rather than crossing into the host platform.
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-facing WordPress plugin flaw (AV:N/PR:N/UI:N); AC:H retained because privilege escalation depends on uncontrolled preconditions, with full C/I/A impact from admin-level takeover.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Unauthenticated Privilege Escalation in GiveWP <= 4.17.0 versions.
Executive ViewAI
GiveWP, a WordPress donation plugin, has a high-severity unauthenticated privilege escalation affecting versions through 4.17.0. A remote attacker could gain elevated access without credentials, putting donor data, donation integrity, and site availability at risk. Because no vendor-released patch identified at time of analysis and no public exploit identified at time of analysis, any organization running the affected plugin should treat this as an urgent exposure.
No vendor-released patch identified at time of analysis; interim mitigations include deactivating or removing GiveWP where not essential, blocking GiveWP privilege-escalation endpoints with WAF or virtual patching, restricting administrative and plugin access to trusted networks, enforcing least privilege, and monitoring for unauthorized privilege changes and new administrator accounts.
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
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
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
Deserialization of Untrusted Data vulnerability in GiveWP GiveWP allows Object Injection.19.3. Rated critical severity (
EUVD-2026-93076
GHSA-gqc7-m99j-qx7h
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB