dbcve.org
GivewpWordPress extension

CVE-2025-22777

CRITICAL · 9.8 CVSS v3.1 Published 2025-01-13
Fix available
A fix is available. Upgrade to 3.19.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Deserialization of Untrusted Data vulnerability in StellarWP GiveWP give allows Object Injection.This issue affects GiveWP: from n/a through <= 3.19.3.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The GiveWP WordPress plugin before version 3.19.3 contains a deserialization vulnerability where untrusted input is passed to PHP's unserialize() function, allowing attackers to inject crafted PHP objects. This object injection can potentially trigger magic methods leading to remote code execution depending on available POP (Property-Oriented Programming) chains in the application.

MitigationUpdate GiveWP to the latest version (3.19.4 or higher) immediately. If immediate updating is not possible, consider disabling the plugin or implementing web application firewall rules to block malicious deserialization payloads.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GivewpWordPress extension
Affected:< 3.19.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check GiveWP plugin version in WordPress admin
    Navigate to Plugins > Installed Plugins in the WordPress admin dashboard. Locate 'GiveWP - Donation Plugin and Fundraising Platform' and read the version number displayed below the plugin name.
    Affected if The displayed version is below 3.19.4 (for example, 3.19.3, 3.19.2, etc.)
  2. Check GiveWP version via plugin file header
    Access the WordPress site via FTP or file manager. Navigate to wp-content/plugins/give and open the main plugin file (typically give.php or index.php). Look for the 'Version:' comment in the file header.
    Affected if The version string shows a number less than 3.19.4
  3. Verify GiveWP plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and confirm the GiveWP plugin has the 'Active' status, or query the wp_options table for option_name='active_plugins' to check if GiveWP is enabled.
    Affected if GiveWP is activated - the vulnerability only affects active installations since inactive plugins do not process requests
  4. Check for suspicious unserialize calls in plugin files (optional advanced check)
    If you have file access, search the give directory for 'unserialize' calls: grep -r 'unserialize' wp-content/plugins/give/ | grep -v '.git'
    Affected if Any unserialize() call that processes input from $_POST, $_GET, $_REQUEST, or database fields without validation is potentially the vulnerable code path

If GiveWP is installed with a version lower than 3.19.4 and the plugin is active, your environment is affected by this deserialization vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.19.4 or later
Fixed in 3.19.4
Interim mitigation

Update GiveWP to the latest version (3.19.4 or higher) immediately. If immediate updating is not possible, consider disabling the plugin or implementing web application firewall rules to block malicious deserialization payloads.

Recommended fix Moderate confidence

GiveWP version 3.19.4

  1. 1. Back up your WordPress database and files before making any changes
  2. 2. Update GiveWP plugin to version 3.19.4 through the WordPress admin dashboard (Plugins > Add New > Upload or directly from the WordPress plugin repository)
  3. 3. Alternatively, update via WP-CLI: wp plugin update give --version=3.19.4
  4. 4. Verify the update was successful by checking the plugin version in Plugins list
  5. 5. Test critical donation workflows to ensure functionality is intact

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Givewp Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-22777 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-22777 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data