Product RecommendationsWordPress extension · Woocommerce
CVE-2023-32744
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in WooCommerce Product Recommendations plugin <= 2.3.0 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 · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in the WooCommerce Product Recommendations plugin versions 2.3.0 and earlier allows attackers to trick authenticated users into performing unintended actions by forcing their browser to send malicious requests.
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
Product RecommendationsWordPress extension
< 2.3.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Verify WooCommerce Product Recommendations plugin is installedLog in to WordPress admin, go to Plugins > Installed Plugins, and look for 'WooCommerce Product Recommendations' in the listAffected if The plugin is not installed or not present in the plugin list
-
Check the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins, find WooCommerce Product Recommendations, and note the version number displayed beneath the plugin nameAffected if The version displayed is 2.3.0 or earlier (any version less than 2.3.0)
-
Confirm the plugin is activeIn Plugins > Installed Plugins, verify that WooCommerce Product Recommendations shows as 'Active' (not 'Inactive' or 'Must-Use')Affected if The plugin is active and the version is less than 2.3.0
A user is affected if the WooCommerce Product Recommendations plugin is installed, active, and running version 2.3.0 or earlier.
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 · scoped2.3.0
Update the WooCommerce Product Recommendations plugin to a version newer than 2.3.0; if no update is available, consider implementing anti-CSRF tokens in plugin forms and requests or temporarily disable the plugin until a fix is released.
Version 2.3.0 or later of WooCommerce Product Recommendations plugin
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the WooCommerce Product Recommendations plugin
- Check the current version to confirm it is below 2.3.0
- If an update is available, click 'Update Now' to upgrade to version 2.3.0 or higher
- Alternatively, download the latest version from the WordPress Plugin Repository or WooCommerce.com
- Deactivate and reinstall the plugin if automatic update does not work
- Verify the new version number after updating
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Product Recommendations
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-32744 — 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-2023-32744 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