Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-104405 Overview
CVE-2026-104405 is an unauthenticated privilege escalation vulnerability affecting the GiveWP WordPress donation plugin in versions 4.17.0 and earlier. The flaw falls under [CWE-266: Incorrect Privilege Assignment] and allows remote attackers without valid credentials to elevate their privileges on affected WordPress sites. Successful exploitation can result in full compromise of the application, including unauthorized administrative access, modification of donation records, and persistent backdoors. GiveWP is widely deployed by nonprofits and fundraising organizations, which expands the exposure surface across the WordPress ecosystem.
Critical Impact
Remote attackers can gain elevated privileges on GiveWP-powered WordPress sites without authentication, enabling full site takeover and potential exposure of donor data.
Affected Products
- GiveWP WordPress plugin (also known as give) versions <= 4.17.0
- WordPress sites with the GiveWP donation plugin installed and activated
- Nonprofit, charity, and fundraising sites relying on GiveWP for payment workflows
Discovery Timeline
- 2026-10-06 - CVE-2026-104405 published to NVD
- 2026-10-06 - Last updated in NVD database
Technical Details for CVE-2026-104405
Vulnerability Analysis
The vulnerability stems from incorrect privilege assignment within the GiveWP plugin. An unauthenticated attacker can interact with a plugin endpoint that fails to properly validate the requester's role or capability. As a result, actions reserved for privileged users become reachable from anonymous HTTP requests. The vulnerability is network-exploitable and requires no user interaction, though exploitation complexity is reported as high, indicating conditions such as specific site configuration or timing must be met for a reliable attack.
Once privilege escalation succeeds, the attacker can perform operations with elevated WordPress capabilities. This typically includes modifying plugin settings, adjusting donation configurations, injecting content, or chaining to administrative actions that enable persistent access.
Root Cause
The root cause is improper enforcement of capability checks on sensitive plugin functionality. The affected code paths do not consistently verify that the requesting user holds the required WordPress capability before performing privileged operations. This mapping failure between request origin and effective privileges aligns with [CWE-266].
Attack Vector
Attackers deliver crafted HTTP requests to vulnerable GiveWP endpoints exposed by the WordPress site. No authentication is required. After successful exploitation, follow-on actions can include creating or modifying privileged accounts, altering donation records, or staging further compromise through WordPress administrative features. Public technical details are available in the Patchstack Plugin Vulnerability Report.
// No verified public exploit code available at time of writing.
// Refer to the Patchstack advisory for technical details.
Detection Methods for CVE-2026-104405
Indicators of Compromise
- Unexpected creation or role modification of WordPress user accounts, especially new accounts with administrator capabilities.
- Anomalous POST requests to GiveWP admin-ajax.php or REST endpoints originating from unauthenticated sessions.
- Unauthorized changes to GiveWP plugin settings, payment gateway configuration, or donation form parameters.
- New or modified PHP files under wp-content/plugins/give/ or in the WordPress uploads directory following suspicious plugin activity.
Detection Strategies
- Review WordPress audit logs for role changes and privilege assignments correlated with GiveWP endpoint traffic.
- Deploy web application firewall (WAF) rules that flag unauthenticated requests invoking GiveWP administrative actions.
- Compare installed give plugin files against known-good hashes from the official WordPress plugin repository.
Monitoring Recommendations
- Forward WordPress, PHP, and web server logs to a centralized analytics platform for correlation and retention.
- Alert on sudden spikes in admin-ajax.php traffic or REST API calls referencing give namespaces.
- Monitor outbound connections from the web host that could indicate post-exploitation command-and-control activity.
How to Mitigate CVE-2026-104405
Immediate Actions Required
- Identify every WordPress instance with the GiveWP plugin installed and confirm the installed version.
- Update GiveWP to a version later than 4.17.0 once the vendor patch is applied through the WordPress plugin updater.
- Rotate administrator credentials and audit all user accounts for unauthorized additions or role changes.
- Review donation records, payment gateway settings, and recently modified plugin or theme files for signs of tampering.
Patch Information
Users should upgrade GiveWP to a release above 4.17.0 that addresses the privilege assignment flaw. Refer to the Patchstack Plugin Vulnerability Report for the current fixed version and vendor advisory references.
Workarounds
- Deactivate and remove the GiveWP plugin until the patched version is deployed if updates cannot be applied immediately.
- Restrict access to WordPress administrative and AJAX endpoints using IP allowlists or authentication at the reverse proxy layer.
- Enable a WordPress-aware WAF with virtual patching rules targeting GiveWP privilege escalation attempts.
# Example: block anonymous access to GiveWP admin-ajax actions at the reverse proxy
# (adapt to your environment and tested allowlist)
location ~ ^/wp-admin/admin-ajax\.php$ {
if ($arg_action ~* "^give_") {
return 403;
}
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

