Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify WordPress site with GiveWP installed
-
ExploitSend unauthenticated HTTP request to unprotected plugin endpoint
-
ExecutionTrigger missing authorization path (CWE-862)
-
ImpactRead or modify restricted donation data
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 | No special conditions are required beyond the target WordPress site having GiveWP installed and running a version prior to 4.16.6. The CVSS vector AV:N/AC:L/PR:N/UI:N confirms remote unauthenticated exploitation against default plugin installations without needing any specific non-default configuration toggle to be enabled. What limits exploitation is the requirement that the target site runs WordPress with GiveWP actively installed and enabled - non-WordPress environments and sites without this plugin are unaffected. The scope-unchanged (S:U) rating further limits impact to within the WordPress application boundary, preventing lateral movement to the underlying server OS. The specific internal endpoints lacking authorization checks are not disclosed in the available references, which provides minor obscurity but should not be relied upon as a defense. |
| Impact | The CVSS 6.5 medium score is supported by a vector of AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N, indicating low-complexity unauthenticated network exploitation with limited but real confidentiality and integrity impact and no availability consequence. No EPSS score was provided in the source data, and this CVE is not listed in the CISA Known Exploited Vulnerabilities catalog, nor is there a known public proof-of-concept - all of which moderates immediate alarm. However, the PR:N/AC:L combination means that once a vulnerable endpoint is fingerprinted, exploitation requires no prior access or special tooling, and even a mid-sized municipal IT team in rybnik running WordPress-based fundraising infrastructure should treat this as urgent patching work rather than a deferred item, given donation platforms often process sensitive donor PII and payment metadata. The scope-unchanged (S:U) rating limits blast radius to the WordPress application context, which prevents privilege escalation to the hosting OS. Overall this is a real priority for GiveWP operators, not a high-CVSS-but-low-real-risk false alarm, given the zero-barrier exploitation path. |
| Exploit ScenarioDerived | An unauthenticated remote attacker enumerates a WordPress site running GiveWP below version 4.16.6, then sends a crafted HTTP request directly to an unprotected plugin endpoint that omits WordPress capability verification. The missing authorization check allows the request to succeed, granting the attacker read or write access to donation records, donor data, or plugin configuration that should be restricted to privileged roles. No public POC has been identified, but the low attack complexity (AC:L) and absence of authentication requirements mean exploitation is straightforward once the unprotected route is discovered. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 18, 2026
Broken access control in GiveWP versions prior to 4.16.6 exposes unauthenticated network attackers to partial read and write access over donation-related functionality, bypassing authorization entirely due to missing capability checks (CWE-862). Reported by Patchstack and tracked under EUVD-2026-60776, the flaw affects all installs of the Nexcess GiveWP WordPress plugin below the patched release. No public exploit code has been identified at time of analysis, and a vendor-released patch is available in version 4.16.6.
RemediationAI
The primary fix is to update GiveWP to version 4.16.6 or later, which contains the vendor-released patch addressing this broken access control. Site administrators should apply the update immediately via the WordPress plugin dashboard or by downloading the patched release from the official plugin repository. The Patchstack advisory at https://patchstack.com/database/wordpress/plugin/give/vulnerability/wordpress-givewp-plugin-4-16-6-broken-access-control-vulnerability-2 provides additional guidance. If immediate patching is operationally blocked, a compensating control is to temporarily deactivate the GiveWP plugin entirely - note this will disable all donation forms and fundraising functionality for the duration. Alternatively, a web application firewall (WAF) rule blocking unauthenticated POST requests to GiveWP-specific endpoints may reduce exposure but requires identifying exact vulnerable routes, which are not publicly disclosed in available references, making this an imprecise mitigation. Patching to 4.16.6 remains the only confirmed complete remediation.
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 management plugin maintained by Nexcess, identified by CPE cpe:2.3:a:nexcess:givewp:*:*:*:*:*:*:*:*. The root cause is CWE-862 (Missing Authorization), a class of flaw where server-side code executes privileged actions without verifying whether the requesting party holds the necessary WordPress capability (e.g., via current_user_can()). In WordPress plugin architecture, this commonly manifests in unprotected REST API endpoints, AJAX action handlers registered without nonce or capability checks, or admin-side routes accessible to unauthenticated users. The CVSS vector AV:N/PR:N confirms the vulnerable code path is reachable over the network without any credentials, consistent with a publicly exposed WordPress endpoint that omits authorization gating.
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:N/UI:N/S:U/C:L/I:L/A:N
Network-reachable unauthenticated endpoint (AV:N, PR:N) with low complexity; limited C:L/I:L reflects partial access bypass without full system compromise or availability impact.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
Lifecycle Timeline
2DescriptionCVE.org
Unauthenticated Broken Access Control in GiveWP < 4.16.6 versions.
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
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-60776
GHSA-h968-wg7c-wxj2
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB