Product AddonsWordPress extension · Woocommerce
CVE-2023-32794
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 Add-Ons plugin <= 6.1.3 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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the WooCommerce Product Add-Ons plugin up to version 6.1.3 allows attackers to trick authenticated store administrators or customers into submitting unintended requests, potentially leading to unauthorized modification of product add-on configurations or order manipulation.
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 AddonsWordPress extension
<= 6.1.3CVSS 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.
-
Check the installed plugin versionIn the WordPress admin dashboard, go to Plugins > Installed Plugins and locate 'WooCommerce Product Add-Ons'. The version number is displayed below the plugin name.Affected if The displayed version is 6.1.3 or lower
-
Verify version via plugin filesAccess the plugin directory via FTP or file manager and open the main plugin file (usually woocommerce-product-add-ons.php) or readme.txt. Look for the 'Version' header comment.Affected if The version in the file header is 6.1.3 or lower
-
Inspect admin forms for CSRF tokensNavigate to the WooCommerce Product Add-Ons settings pages in the admin panel. View the page source (right-click > View Page Source) and examine form elements for hidden input fields containing nonce or CSRF token values.Affected if Forms on plugin settings pages lack hidden nonce or CSRF token input fields
-
Check AJAX requests for token validationUse browser developer tools (Network tab). Perform an action in the plugin (such as saving add-on settings). Examine the AJAX request to admin-ajax.php for a '_wpnonce' or 'security' parameter in the request data.Affected if AJAX requests to plugin endpoints do not include a valid nonce or security token parameter
You are affected if the installed WooCommerce Product Add-Ons version is 6.1.3 or lower and the plugin forms and AJAX requests lack CSRF token validation.
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.
From vendor dataUpdate the WooCommerce Product Add-Ons plugin to the latest version which includes anti-CSRF token validation for all form submissions and AJAX requests.
Fix this in Product Addons
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-32794 — 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-32794 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