dbcve.org
Woocommerce Multiple Free GiftWordPress extension · Lilmonkee

CVE-2022-3459

MEDIUM · 5.3 CVSS v3.1 Published 2024-09-14
Fix available
A fix is available. Upgrade to after 1.2.3 or later.
See remediation →
62/100
Remediation priority · Elevated
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
The WooCommerce Multiple Free Gift plugin for WordPress is vulnerable to gift manipulation in all versions up to, and including, 1.2.3. This is due to plugin not enforcing server-side checks on the products that can be added as a gift. This makes it possible for unauthenticated attackers to add non-gift items to their cart as a gift.

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

The WooCommerce Multiple Free Gift plugin fails to perform server-side validation on which products can be added as gifts to the shopping cart. This allows unauthenticated attackers to manipulate the cart logic and add arbitrary products as 'free gifts' instead of only the intended promotional items, resulting in unauthorized discounts and inventory theft.

MitigationImplement server-side validation to verify that only products designated as valid gifts can be added via the gift functionality. Consider rate limiting and monitoring cart modifications until a patch is available.

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 Multiple Free GiftWordPress extension
Affected:<= 1.2.3

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
None
Integrity
Low
Availability
None

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

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. Verify plugin is installed
    Check the WordPress plugins directory for the Lilmonkee Woocommerce Multiple Free Gift plugin. This is typically located in wp-content/plugins/ directory. Look for a folder containing 'lilmonkee' and 'free-gift' in the name.
    Affected if The plugin folder exists in the WordPress plugins directory
  2. Check installed version
    Open the main plugin PHP file and look for the version comment in the file header, or check the readme.txt file in the plugin folder for the 'Stable tag' or 'Version' entry. Compare this version number to the affected range <= 1.2.3.
    Affected if The installed version is 1.2.3 or lower
  3. Confirm WooCommerce is active
    Verify that WooCommerce is installed and active on the WordPress site. The vulnerability only affects environments where WooCommerce is running alongside this plugin.
    Affected if WooCommerce is active and the vulnerable plugin is installed
  4. Check for cart manipulation indicators
    Review server access logs and WooCommerce order logs for unusual cart modification patterns. Look for POST requests to /?add-to-cart= with unexpected product IDs, especially in bulk or rapid succession from the same IP. Also inspect recent orders for suspicious discounts or free gift claims.
    Affected if Cart modifications include product IDs that were not designated as valid promotional gifts, or unusual patterns of cart additions involving the add-to-cart parameter

A user is affected if the Lilmonkee Woocommerce Multiple Free Gift plugin version 1.2.3 or lower is installed on a WordPress site with WooCommerce active, and cart/logic analysis shows unauthorized products being added as free gifts.

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 1.2.3
Interim mitigation

Implement server-side validation to verify that only products designated as valid gifts can be added via the gift functionality. Consider rate limiting and monitoring cart modifications until a patch is available.

Recommended fix Moderate confidence

Latest version of WooCommerce Multiple Free Gift plugin (after 1.2.3)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'WooCommerce Multiple Free Gift' plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, navigate to Plugins > Add New > Upload Plugin and upload the latest version from wordpress.org/plugins/woocommerce-multiple-free-gift
  6. 6. After updating, verify the cart functionality works correctly with legitimate gift items

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

Fix this in Woocommerce Multiple Free Gift Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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