dbcve.org
GivewpWordPress extension

CVE-2024-37099

CRITICAL · 9.8 CVSS v3.1 Published 2024-08-19
Fix available
A fix is available. Upgrade to 3.14.2 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 Liquid Web GiveWP allows Object Injection.This issue affects GiveWP: from n/a through 3.14.1.

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

A deserialization vulnerability in GiveWP plugin allows attackers to inject PHP objects via untrusted data, potentially leading to remote code execution. This is a critical PHP object injection flaw through unsafe use of unserialize() on user-controlled data.

MitigationUpgrade GiveWP to version 3.14.2 or later. If immediate upgrade is not possible, disable the plugin or implement web application firewall rules to block serialized data in requests.

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

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. Locate GiveWP plugin installation
    Check your WordPress plugins directory (wp-content/plugins) for a folder named 'give' or 'givewp'. You can also list installed plugins via WP-CLI: wp plugin list --name='give'
    Affected if The 'give' or 'givewp' folder exists in the plugins directory
  2. Determine installed GiveWP version
    Read the plugin version from the main plugin file header (usually givewp/give.php or givewp/index.php). You can also query it via database: SELECT option_value FROM wp_options WHERE option_name = 'give_version' OR query via WP-CLI: wp plugin get give --format=json
    Affected if The version returned is lower than 3.14.2 or cannot be determined to be 3.14.2 or higher
  3. Verify plugin is active
    Check if the plugin is currently enabled in WordPress. Via WP-CLI: wp plugin is-active give. Or check database: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins' AND option_value LIKE '%give%'
    Affected if The plugin is active and the version is below 3.14.2
  4. Confirm vulnerability scope
    This vulnerability is exploitable through any user-supplied data that reaches the plugin's unserialize() call. The flaw exists in core plugin code, not a specific configuration toggle. No additional feature flags need to be enabled for the flaw to exist.
    Affected if GiveWP is installed, active, and running a version below 3.14.2

If GiveWP plugin is installed and active with a version lower than 3.14.2, your environment is affected by this PHP object injection 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.14.2 or later
Fixed in 3.14.2
Interim mitigation

Upgrade GiveWP to version 3.14.2 or later. If immediate upgrade is not possible, disable the plugin or implement web application firewall rules to block serialized data in requests.

Recommended fix High confidence

GiveWP 3.14.2

  1. 1. Back up your WordPress site and database before performing any updates.
  2. 2. Navigate to the WordPress admin dashboard > Plugins section.
  3. 3. Locate the GiveWP plugin and check if version 3.14.2 is available.
  4. 4. If an update is available, update GiveWP to version 3.14.2.
  5. 5. Alternatively, download GiveWP version 3.14.2 from the official WordPress repository or GiveWP website and upload it via WordPress > Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the plugin version shows 3.14.2 in the plugins list.
  7. 7. Test critical donation workflows to ensure functionality is intact.
Caveat Review GiveWP 3.14.2 release notes for any potential breaking changes or deprecations before upgrading in production environments.

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

Fix this in Givewp Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-37099 — 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-2024-37099 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