dbcve.org
Wishlist For WoocommerceWordPress extension · Wpfactory

CVE-2024-13774

MEDIUM · 6.5 CVSS v3.1 Published 2025-03-08
Fix available
A fix is available. Upgrade to 3.1.8 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Wishlist for WooCommerce: Multi Wishlists Per Customer plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.1.7. This is due to missing or incorrect nonce validation on the 'save_to_multiple_wishlist' function. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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 Wishlist for WooCommerce plugin lacks proper nonce validation in its 'save_to_multiple_wishlist' function, allowing unauthenticated attackers to forge administrative requests. This CSRF vulnerability enables attackers to modify plugin settings and inject malicious scripts by tricking administrators into clicking crafted links.

MitigationUpdate to the latest plugin version when available and ensure all state-changing functions implement proper nonce verification with wp_verify_nonce or check_admin_referer.

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
Wishlist For WoocommerceWordPress extension
Affected:< 3.1.8

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
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 Wishlist for WooCommerce plugin is installed
    Navigate to Plugins > Installed Plugins in WordPress admin and look for 'Wishlist for WooCommerce' by Wpfactory, or check the filesystem at wp-content/plugins/wishlist-for-woocommerce/ for the main plugin file
    Affected if Plugin is not installed or not present in the expected location
  2. Identify installed plugin version
    In WordPress admin, view the plugin details from the Plugins page to see the version number, or open the main plugin PHP file (e.g., wishlist-for-woocommerce.php) and locate the 'Version' header in the plugin comment block
    Affected if Version is less than 3.1.8 (e.g., 3.1.7, 3.1.6, etc.)
  3. Confirm vulnerable function exists
    Access the plugin files via FTP or file manager, then open includes/class-wishlist-for-woocommerce.php or similar main class file and search for the function named 'save_to_multiple_wishlist'
    Affected if The function 'save_to_multiple_wishlist' exists in the plugin code
  4. Check for missing nonce validation in the vulnerable function
    Open the file containing 'save_to_multiple_wishlist' and examine the function body. Look for absence of wp_verify_nonce, check_admin_referer, or wp_nonce_field calls at the beginning of the function before any data processing
    Affected if No nonce verification (wp_verify_nonce or check_admin_referer) is present at the start of the save_to_multiple_wishlist function

User is affected if the Wishlist for WooCommerce plugin is installed with a version prior to 3.1.8 AND the save_to_multiple_wishlist function exists without proper nonce validation checks.

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.1.8 or later
Fixed in 3.1.8
Interim mitigation

Update to the latest plugin version when available and ensure all state-changing functions implement proper nonce verification with wp_verify_nonce or check_admin_referer.

Recommended fix High confidence

3.1.8

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Wishlist for WooCommerce: Multi Wishlists Per Customer' plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to version 3.1.8
  5. 5. Alternatively, download version 3.1.8 from the WordPress Plugin Repository and upload/install it manually
  6. 6. After updating, verify the plugin is running version 3.1.8 under Plugins > Installed Plugins

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

Fix this in Wishlist For Woocommerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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