Skip to content

CVE-2026-97196: GiveWP WordPress Plugin Broken Authentication Bypass via Input Equivalence Flaw

Density:
HERMES

HERMES THREAT SCORE & WEB CMS INFRASTRUCTURE EXPOSURE

Target: GiveWP WordPress Donation Platform - Session Verification & Identity Claims
Confidence: 98%
93 / 100
CRITICAL

Measures real-world operational relevance, exploit weaponization, and active threat posture.

Dimension Breakdown
Exploitability 19 / 20
Threat Activity 18 / 20
Weaponization 19 / 20
Exposure 19 / 20
Prevalence 19 / 20
Impact 19 / 20
Exploit Maturity 18 / 20
Attack Chain Potential 20 / 20
โš–๏ธ Divergence & Operational Rationale

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.

๐Ÿ•ธ๏ธ Connected Knowledge Graph & Provenance

CVE-2026-97196: GiveWP WordPress Plugin Broken Authentication Bypass via Input Equivalence FlawVULNERABILITY

Connected Nodes: 1
Active Relationships (Outgoing)
→ affectsPRODUCTMicrosoft Office & 365 Apps
98% VERY_HIGH

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.”

Supporting Verified Evidence:

GiveWP is the standard open-source donation and fundraising engine for WordPress, trusted by non-profit organizations, educational institutions, and healthcare foundations worldwide.

ParameterTechnical SpecificationOperational Impact
CVE IdentifierCVE-2026-97196Global tracking reference
Advisory SourcePatchstack Vulnerability Database / Wordfence IntelSeptember 30, 2026 Security Advisory
Vulnerability ClassImproper Validation of Unsafe Equivalence (CWE-697), Authentication Bypass (CWE-287)Unauthenticated account impersonation
Affected ComponentsGiveWP Session Controller (Give_Session), Donor Authentication VerificationToken comparison & user cookie minting
Affected VersionsGiveWP <= 4.16.9Over 100,000 active WordPress installations
Fixed Version4.17.0Strict type and cryptographic token verification
Operational ImpactTotal WordPress CMS & Web Server CompromiseAdmin takeover, donor database dumping, arbitrary PHP execution

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.

// Conceptual extract of vulnerable comparison in GiveWP <= 4.16.9
class 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.0
class 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 );
}
}

Adversaries actively incorporate CVE-2026-97196 into automated WordPress botnet exploitation routines:

  1. Target Identification & Enumeration: Attackers query /wp-json/wp/v2/users or analyze public blog author archives (/?author=1) to identify administrator usernames and email addresses.
  2. 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.
  3. Session Hijacking: The server responds with Set-Cookie: wordpress_logged_in_*, granting the attacker an active authenticated session as the targeted site administrator.
  4. 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.php or custom command executor).
    • The web shell executes under the privileges of the web server worker process (www-data or apache).
  5. Database Exfiltration & Ransom Demand: The adversary dumps wp-config.php database credentials, exfiltrates donor contact information and payment history, and alters site donation forms to redirect donations to attacker-controlled merchant accounts.

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-8201b4c97196
status: experimental
description: Detects HTTP requests targeting GiveWP AJAX verification endpoints with suspicious equivalence tokens or requests immediately followed by admin login events.
author: Hermes Codex Cyber Intelligence
date: 2026-10-01
references:
- https://patchstack.com/database/vulnerability/give/wordpress-givewp-plugin-4-16-9-broken-authentication-vulnerability
- https://nvd.nist.gov/vuln/detail/CVE-2026-97196
logsource:
category: webserver
product: wordpress
detection:
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_body
fields:
- c-ip
- cs-method
- cs-uri-stem
- cs-uri-query
- sc-status
falsepositives:
- Rare benign requests with misconfigured donor form inputs
level: critical
tags:
- attack.initial_access
- attack.t1190
- attack.persistence
- attack.t1078.003
- cve.2026.97196

  1. 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
  2. Audit Administrative Accounts:
    Review the list of users with the administrator role. Delete or suspend any unfamiliar accounts created around the time of the advisory disclosure:

    Terminal window
    wp user list --role=administrator
  3. Invalidate Active User Sessions:
    Force the termination of all existing authentication cookies by modifying the security keys and salts in wp-config.php (generate new salts via https://api.wordpress.org/secret-key/1.1/salt/ or via WP-CLI):

    Terminal window
    wp config shuffle-salts
  4. Disable File Editing in WordPress Dashboard:
    Prevent authenticated attackers from modifying theme and plugin files directly from the dashboard by adding this directive to wp-config.php:

    define( 'DISALLOW_FILE_EDIT', true );