dbcve.org
Giveaway BoostWordPress extension · Giveawayboost

CVE-2024-49332

CRITICAL · 9.8 CVSS v3.1 Published 2024-10-20
Fix available
A fix is available. Upgrade to after 2.1.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 giveawayboost Giveaway Boost giveaway-boost allows Object Injection.This issue affects Giveaway Boost: from n/a through <= 2.1.4.

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 · moderate confidence

A PHP Object Injection vulnerability in the Giveaway Boost WordPress plugin (versions up to 2.1.4) allows unauthenticated attackers to deserialize untrusted data, potentially leading to remote code execution via malicious serialized PHP objects.

MitigationReplace insecure unserialize() calls with json_decode() for data handling, or update to a patched version if available. Validate all input and implement allowlist filtering for any remaining deserialization operations.

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
Giveaway BoostWordPress extension
Affected:<= 2.1.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. Confirm Giveaway Boost plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Giveaway Boost' or check the filesystem under wp-content/plugins/ for a folder named 'giveaway-boost' or similar
    Affected if The plugin is present in the WordPress installation
  2. Identify the installed version
    Check the plugin header in the main PHP file (often named giveway-boost.php or similar in the plugin folder) for the 'Version' field, or view the plugin in WordPress admin which displays the version number
    Affected if The version number is 2.1.4 or lower
  3. Verify the vulnerable unserialize() call exists
    Search the plugin source code files for calls to unserialize() function, particularly those handling request parameters, cookie values, or external input
    Affected if The plugin contains unserialize() calls that process untrusted input without prior validation
  4. Confirm the deserialization accepts user input
    Examine the unserialize() calls found and trace whether the data being deserialized comes from unauthenticated sources such as GET/POST parameters, cookies, or HTTP headers
    Affected if The unserialize() function receives data directly from user requests without sanitization
  5. Check if any input validation or allowlisting is present
    Review the code around the unserialize() calls to see if json_decode() has replaced unserialize(), or if there is any allowlist/validation logic filtering the input before deserialization
    Affected if No json_decode() replacement or input validation exists, and unserialize() still processes untrusted data

The environment is affected if the Giveaway Boost plugin (versions 2.1.4 or lower) is installed and contains insecure unserialize() calls processing unauthenticated user input without validation.

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 a release after 2.1.4
Interim mitigation

Replace insecure unserialize() calls with json_decode() for data handling, or update to a patched version if available. Validate all input and implement allowlist filtering for any remaining deserialization operations.

Recommended fix Low confidence

Latest available version from WordPress plugin repository (vendor should have released a fix after 2.1.4)

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to the WordPress admin dashboard > Plugins.
  3. 3. Locate the 'Giveaway Boost' plugin in the installed plugins list.
  4. 4. Check if an update is available. If so, update to the latest version.
  5. 5. Verify the update was successful and the plugin is functioning correctly.
  6. 6. If no update is available through WordPress, check the official WordPress plugin repository or contact the plugin developer for the latest secure version.

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

Fix this in Giveaway Boost Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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