dbcve.org
Wpc Smart Wishlist For WoocommerceWordPress extension · Wpclever

CVE-2023-34386

HIGH · 8.8 CVSS v3.1 Published 2023-11-09
Fix available
A fix is available. Upgrade to 4.7.2 or later.
See remediation →
95/100
Remediation priority · Urgent
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
Cross-Site Request Forgery (CSRF) vulnerability in WPClever WPC Smart Wishlist for WooCommerce plugin <= 4.7.1 versions.

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

Cross-Site Request Forgery (CSRF) vulnerability in the WPClever WPC Smart Wishlist for WooCommerce plugin affecting versions up to and including 4.7.1. The vulnerability allows attackers to trick authenticated users into performing unwanted actions on the wishlist functionality, such as adding or removing items without their consent.

MitigationUpdate the WPC Smart Wishlist for WooCommerce plugin to a version newer than 4.7.1. Review user sessions and consider implementing anti-CSRF tokens in custom code if the vendor update is delayed.

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
Wpc Smart Wishlist For WoocommerceWordPress extension
Affected:< 4.7.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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Check the installed plugin version
    Log into the WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate 'Wpc Smart Wishlist For Woocommerce' and view the version number displayed under the plugin name. Alternatively, inspect the plugin's main PHP file header or use WP-CLI: `wp plugin list --name=wpc-smart-wishlist`
    Affected if The version displayed is 4.7.1 or lower
  2. Verify WooCommerce is active
    In the WordPress admin under Plugins > Installed Plugins, confirm that WooCommerce is installed and activated. The WPC Smart Wishlist plugin requires WooCommerce to function.
    Affected if WooCommerce is active and the wishlist plugin is installed
  3. Confirm wishlist functionality is enabled
    Visit the site frontend and attempt to use wishlist features (look for wishlist buttons on product pages, check for a wishlist page/link, or inspect browser cookies/localStorage for wishlist-related identifiers). In admin, check plugin settings under WPC Menu > Smart Wishlist to see if the wishlist feature is configured.
    Affected if Wishlist functionality is configured and accessible to logged-in users on the site

If the installed version is below 4.7.2, WooCommerce is active, and the wishlist feature is enabled for authenticated users, the environment is vulnerable to CVE-2023-34386.

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 4.7.2 or later
Fixed in 4.7.2
Interim mitigation

Update the WPC Smart Wishlist for WooCommerce plugin to a version newer than 4.7.1. Review user sessions and consider implementing anti-CSRF tokens in custom code if the vendor update is delayed.

Recommended fix High confidence

4.7.2

  1. 1. Create a full backup of your WordPress site (database and files) before updating any plugins.
  2. 2. Navigate to your WordPress admin dashboard > Plugins > Installed Plugins.
  3. 3. Locate 'WPC Smart Wishlist for WooCommerce' in the plugin list.
  4. 4. If an update is available, click 'Update Now' to update the plugin to version 4.7.2 or later.
  5. 5. Alternatively, download version 4.7.2 or higher from the WordPress plugin repository and upload it manually via Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the plugin version in the plugins list to confirm the update was successful.
  7. 7. Test the wishlist functionality on your site to ensure the update did not break any expected features.

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

Fix this in Wpc Smart Wishlist For Woocommerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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