Woocommerce Ultimate Gift CardWordPress extension · Wpswings
CVE-2024-8425
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 · uneditedThe WooCommerce Ultimate Gift Card plugin for WordPress is vulnerable to arbitrary file uploads due to insufficient file type validation in the 'mwb_wgm_preview_mail' and 'mwb_wgm_woocommerce_add_cart_item_data' functions in all versions up to, and including, 2.9.2. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible. Please note that this may have been patched on an older version than 2.9.2, however, we do not have access to older versions of the software to confirm when the patch was added. The only patched version we have confirmed is 2.9.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 confidenceThe WooCommerce Ultimate Gift Card plugin for WordPress versions up to 2.9.2 contains arbitrary file upload vulnerabilities in the 'mwb_wgm_preview_mail' and 'mwb_wgm_woocommerce_add_cart_item_data' functions due to insufficient file type validation. This critical flaw allows unauthenticated attackers to upload malicious files to the server, potentially achieving remote code execution.
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
Woocommerce Ultimate Gift CardWordPress extension
<= 2.6.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm the plugin is installedNavigate to WordPress admin > Plugins and look for 'Wpswings Woocommerce Ultimate Gift Card' or inspect the directory wp-content/plugins/ for a folder containing 'gift-card' or 'wgm' in the nameAffected if The plugin is present in the WordPress installation
-
Check the installed versionIn WordPress admin > Plugins, find the Ultimate Gift Card plugin and view its version number. Alternatively, check the main plugin PHP file for the 'Version' header in the plugin commentsAffected if The version number is 2.6.0 or lower
-
Determine if the plugin is activeIn WordPress admin > Plugins, verify whether the Ultimate Gift Card plugin is currently activatedAffected if The plugin is activated and running
-
Inspect uploaded files for suspicious contentCheck the wp-content/uploads/ directory (and any custom upload directories) for unfamiliar PHP files, shell scripts, or files with double extensions like image.php.jpg. Use grep to search for PHP opening tags in uploaded filesAffected if Unexpected PHP files or scripts exist in upload directories
-
Review access logs for exploitation attemptsExamine web server access logs for POST requests to endpoints containing 'mwb_wgm_preview_mail' or 'mwb_wgm_woocommerce_add_cart_item_data', or requests with file uploads to these functionsAffected if Log entries show file upload requests to the vulnerable functions, especially from unauthorized IP addresses
You are affected if the WooCommerce Ultimate Gift Card plugin is installed with version 2.6.0 or lower and is currently active, as this allows the arbitrary file upload vulnerability to be exploited.
Generated from the published advisory. Verify against your own configuration.
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 · scopedImmediately update the WooCommerce Ultimate Gift Card plugin to version 2.9.3 or later to patch the arbitrary file upload vulnerability. Until the update is applied, consider disabling the plugin or implementing web application firewall rules to block suspicious file upload requests.
WooCommerce Ultimate Gift Card version 2.9.3 or later
- Create a full backup of your WordPress site, including database and files
- Navigate to Plugins > Installed Plugins in WordPress admin
- Find 'WooCommerce Ultimate Gift Card' plugin and click 'Update now' if an update is available
- Alternatively, download version 2.9.3 from the official WordPress plugin repository or CodeCanyon
- Deactivate and delete the current version, then upload and install version 2.9.3
- Activate the plugin after installation
- Verify the plugin version shows 2.9.3 or higher in the plugins list
- Test gift card creation and email preview functionality to confirm the fix works
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Woocommerce Ultimate Gift Card
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-8425 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-8425 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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