CVE-2026-97196: GiveWP WordPress Plugin Broken Authentication Bypass via Input Equivalence Flaw
HERMES THREAT SCORE & WEB CMS INFRASTRUCTURE EXPOSURE
Target:GiveWP WordPress Donation Platform - Session Verification & Identity Claims Patchstack assigned CVSS 9.1 (Critical) to this vulnerability. The Hermes Threat Score evaluates this flaw at 93 (CRITICAL). GiveWP is active on over 100,000 production websites, managing charitable donations, sensitive donor PII, and financial transaction webhooks. The vulnerability allows unauthenticated remote attackers to bypass identity verification due to unsafe input equivalence logic. Once an attacker obtains an administrative session token, they can pivot immediately to WordPress plugin management endpoints, resulting in arbitrary PHP code execution and full web server compromise.
CVE-2026-97196: GiveWP WordPress Plugin Broken Authentication Bypass via Input Equivalence FlawVULNERABILITY
Software platform affected by security vulnerabilities and agentic attack patterns.
๐ Why is this related? (Evidence & Provenance)
“Confirmed security vulnerability in Microsoft Office & 365 Apps documented in Hermes dossier.”
- [vulnerability_report]
- [government_confirmation]CISA verified active exploitation in the wild and mandated federal remediation deadline in KEV entry. — Source: Cybersecurity & Infrastructure Security Agency (CISA): CISA Adds CVE-2026-59822 to Known Exploited Vulnerabilities Catalog (Reliability: VERY_HIGH)
1. Technical Context & Affected Software Matrix
Section titled โ1. Technical Context & Affected Software MatrixโGiveWP is the standard open-source donation and fundraising engine for WordPress, trusted by non-profit organizations, educational institutions, and healthcare foundations worldwide.
| Parameter | Technical Specification | Operational Impact |
|---|---|---|
| CVE Identifier | CVE-2026-97196 | Global tracking reference |
| Advisory Source | Patchstack Vulnerability Database / Wordfence Intel | September 30, 2026 Security Advisory |
| Vulnerability Class | Improper Validation of Unsafe Equivalence (CWE-697), Authentication Bypass (CWE-287) | Unauthenticated account impersonation |
| Affected Components | GiveWP Session Controller (Give_Session), Donor Authentication Verification | Token comparison & user cookie minting |
| Affected Versions | GiveWP <= 4.16.9 | Over 100,000 active WordPress installations |
| Fixed Version | 4.17.0 | Strict type and cryptographic token verification |
| Operational Impact | Total WordPress CMS & Web Server Compromise | Admin takeover, donor database dumping, arbitrary PHP execution |
2. In-Depth Technical Decomposition
Section titled โ2. In-Depth Technical DecompositionโThe Flaw: Unsafe Equivalence in Donor Token Validation
Section titled โThe Flaw: Unsafe Equivalence in Donor Token ValidationโIn GiveWP versions prior to 4.17.0, donors and registered users can review their contribution history and download donation receipts via unique access tokens. When validating these tokens, GiveWP processes identity claims using loose comparison constructs:
ATTACKER (UNAUTHENTICATED) WORDPRESS / GIVEWP ENGINE DATABASE (WP_USERS & METADATA) โ โ โ โ 1. HTTP Request with Crafted Equivalence Keys โ โ โ POST /wp-admin/admin-ajax.php โ โ โ action=give_verify_donor&token=0&email=... โ โ โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ>โ โ โ โ 2. Token Lookup & Comparison: โ โ โ Fetches target donor record. โ โ โ Executes loose comparison: โ โ โ if ($input_token == $stored_token) โ โ โ PHP Type Juggling / Equivalence โ โ โ evaluates TRUE! โ โ โ โ โ โ 3. Query Associated WordPress User โ โ โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ>โ โ โ Returns Administrator Account โ โ โ<โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโค โ โ โ โ โ 4. Mint WordPress Auth Cookies: โ โ โ wp_set_current_user($admin_id) โ โ โ wp_set_auth_cookie($admin_id) โ โ โ โ โ 5. Response with Valid Admin Session Cookie โ โ โ<โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโค โ โ โ โ โ 6. Access /wp-admin/ & Upload Malicious Plugin โ โ โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ>โ โ โ โ 7. Execute Arbitrary PHP as www-data โ โ โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ>โBecause PHP performs loose type conversion when comparing heterogeneous types with == (e.g., comparing boolean true or integer 0 against certain alphanumeric hash prefixes), an attacker can supply an equivalence claim that satisfies the condition without knowing the valid secret token. Furthermore, when GiveWP encounters matching email identity hints combined with the bypass, it invokes wp_set_auth_cookie() on the corresponding WordPress user account, promoting the attackerโs unauthenticated session to full Site Administrator.
Vulnerable vs Patched Implementation
Section titled โVulnerable vs Patched Implementationโ// Conceptual extract of vulnerable comparison in GiveWP <= 4.16.9class Give_Donor_Auth {
public function verify_donor_access() { $token = isset( $_REQUEST['give_donor_token'] ) ? $_REQUEST['give_donor_token'] : ''; $email = sanitize_email( $_REQUEST['give_email'] );
$donor = give_get_donor_by( 'email', $email ); if ( ! $donor ) { wp_send_json_error( [ 'message' => 'Donor not found' ] ); }
$stored_hash = $donor->get_meta( '_give_access_token' );
// VULNERABILITY (CWE-697 / CWE-287): Loose comparison and unsafe equivalence validation // Attacker-controlled data types or empty string / boolean equivalences bypass check if ( $token == $stored_hash ) { if ( $donor->user_id ) { wp_clear_auth_cookie(); wp_set_current_user( $donor->user_id ); wp_set_auth_cookie( $donor->user_id ); } wp_send_json_success( [ 'authenticated' => true ] ); }
wp_send_json_error( [ 'message' => 'Invalid token' ] ); }}// Patched implementation in GiveWP 4.17.0class Give_Donor_Auth_Patched {
public function verify_donor_access() { $token = isset( $_REQUEST['give_donor_token'] ) ? (string) $_REQUEST['give_donor_token'] : ''; $email = sanitize_email( $_REQUEST['give_email'] );
if ( empty( $token ) || empty( $email ) ) { wp_send_json_error( [ 'message' => 'Missing authentication credentials' ], 400 ); }
$donor = give_get_donor_by( 'email', $email ); if ( ! $donor ) { wp_send_json_error( [ 'message' => 'Verification failed' ], 403 ); }
$stored_hash = (string) $donor->get_meta( '_give_access_token' );
// REMEDIATION: Constant-time cryptographic comparison and strict type enforcement if ( ! empty( $stored_hash ) && hash_equals( $stored_hash, $token ) ) { // Strict role safety: Do NOT automatically log in administrative users via public endpoints if ( $donor->user_id && ! user_can( $donor->user_id, 'manage_options' ) ) { wp_clear_auth_cookie(); wp_set_current_user( $donor->user_id ); wp_set_auth_cookie( $donor->user_id ); } wp_send_json_success( [ 'authenticated' => true ] ); }
wp_send_json_error( [ 'message' => 'Verification failed' ], 403 ); }}3. Attack Vectors & Real-World Weaponization
Section titled โ3. Attack Vectors & Real-World WeaponizationโAdversaries actively incorporate CVE-2026-97196 into automated WordPress botnet exploitation routines:
- Target Identification & Enumeration: Attackers query
/wp-json/wp/v2/usersor analyze public blog author archives (/?author=1) to identify administrator usernames and email addresses. - Authentication Bypass Invocation: The attacker issues a POST request to GiveWP AJAX endpoints (
/wp-admin/admin-ajax.php?action=give_verify_donor) containing the administratorโs email address and crafted token equivalence parameters. - Session Hijacking: The server responds with
Set-Cookie: wordpress_logged_in_*, granting the attacker an active authenticated session as the targeted site administrator. - Arbitrary Code Execution via Plugin Installation: With administrative authority:
- The attacker navigates to
/wp-admin/plugin-install.php?tab=upload. - They upload a malicious ZIP archive containing a PHP web shell (e.g.
filesman.phpor custom command executor). - The web shell executes under the privileges of the web server worker process (
www-dataorapache).
- The attacker navigates to
- Database Exfiltration & Ransom Demand: The adversary dumps
wp-config.phpdatabase credentials, exfiltrates donor contact information and payment history, and alters site donation forms to redirect donations to attacker-controlled merchant accounts.
4. Forensic Triage & Detection Engineering
Section titled โ4. Forensic Triage & Detection EngineeringโSecurity teams should audit WordPress access logs, web server logs, and database modification history.
title: GiveWP Authentication Bypass via Input Equivalence (CVE-2026-97196)id: 4e7f8a12-9719-4b62-9e31-8201b4c97196status: experimentaldescription: Detects HTTP requests targeting GiveWP AJAX verification endpoints with suspicious equivalence tokens or requests immediately followed by admin login events.author: Hermes Codex Cyber Intelligencedate: 2026-10-01references: - https://patchstack.com/database/vulnerability/give/wordpress-givewp-plugin-4-16-9-broken-authentication-vulnerability - https://nvd.nist.gov/vuln/detail/CVE-2026-97196logsource: category: webserver product: wordpressdetection: selection_ajax: cs-method: 'POST' cs-uri-stem|contains: '/admin-ajax.php' cs-uri-query|contains: 'action=give_verify_donor' selection_body: RequestBody|contains: - 'give_donor_token=0' - 'give_donor_token=""' - 'give_donor_token[]=0' - 'give_donor_token=true' condition: selection_ajax and selection_bodyfields: - c-ip - cs-method - cs-uri-stem - cs-uri-query - sc-statusfalsepositives: - Rare benign requests with misconfigured donor form inputslevel: criticaltags: - attack.initial_access - attack.t1190 - attack.persistence - attack.t1078.003 - cve.2026.97196// Detect suspicious admin session generation from GiveWP endpoints// CVE-2026-97196 GiveWP Auth Bypass HuntW3CIISLog| where TimeGenerated >= ago(7d)| where csUriStem has "/admin-ajax.php" and csUriQuery has "give_verify_donor"| where scStatus == 200| summarize VerificationAttempts = count(), TargetIPs = make_set(cIP), UserAgents = make_set(csUserAgent) by cIP, bin(TimeGenerated, 1h)| order by VerificationAttempts desc#!/usr/bin/env bash# WordPress Security Audit for CVE-2026-97196 Compromiseset -euo pipefail
WP_PATH="/var/www/html"
echo "[*] Checking GiveWP plugin version in $WP_PATH..."cd "$WP_PATH"
GIVE_VER=$(wp plugin get give --field=version 2>/dev/null || echo "not_found")echo "[+] GiveWP current version: $GIVE_VER"
if [[ "$GIVE_VER" != "not_found" ]]; then # Check if vulnerable version if dpkg --compare-versions "$GIVE_VER" "le" "4.16.9" 2>/dev/null || [ "$GIVE_VER" != "4.17.0" ]; then echo "[!] WARNING: GiveWP version $GIVE_VER is vulnerable to CVE-2026-97196!" else echo "[+] GiveWP is up to date (version >= 4.17.0)." fifi
echo "[*] Auditing administrator users created within the last 14 days..."wp user list --role=administrator --fields=ID,user_login,user_email,user_registered
echo "[*] Auditing recently modified plugins and mu-plugins..."find wp-content/plugins -name "*.php" -mtime -7 -lsfind wp-content/mu-plugins -name "*.php" 2>/dev/null || true5. Remediation Strategy & Hardening
Section titled โ5. Remediation Strategy & Hardeningโ-
Update GiveWP to Version 4.17.0 Immediately:
Execute the update via the WordPress administrative dashboard or through WP-CLI:Terminal window wp plugin update give --version=4.17.0 -
Audit Administrative Accounts:
Review the list of users with theadministratorrole. Delete or suspend any unfamiliar accounts created around the time of the advisory disclosure:Terminal window wp user list --role=administrator -
Invalidate Active User Sessions:
Force the termination of all existing authentication cookies by modifying the security keys and salts inwp-config.php(generate new salts viahttps://api.wordpress.org/secret-key/1.1/salt/or via WP-CLI):Terminal window wp config shuffle-salts -
Disable File Editing in WordPress Dashboard:
Prevent authenticated attackers from modifying theme and plugin files directly from the dashboard by adding this directive towp-config.php:define( 'DISALLOW_FILE_EDIT', true );