Product AddonsWordPress extension · Woocommerce
CVE-2023-32795
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 · uneditedDeserialization of Untrusted Data vulnerability in WooCommerce Product Add-Ons.This issue affects Product Add-Ons: from n/a through 6.1.3.
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 confidenceA deserialization vulnerability in the WooCommerce Product Add-Ons plugin (versions through 6.1.3) allows processing of untrusted serialized data, potentially leading to remote code execution or other injection attacks.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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.
-
Confirm the plugin is installedCheck your WordPress installation for the WooCommerce Product Add-Ons plugin. This can be done via the WordPress admin dashboard under Plugins, or by checking for the plugin directory in wp-content/plugins/Affected if The plugin is not present in the installation
-
Identify the installed versionRetrieve the currently installed version number of the WooCommerce Product Add-Ons plugin. In WordPress, this is typically visible in the plugin list view in the admin dashboard, or can be queried from the database (wp_options table) under the option_name containing the plugin version.Affected if Unable to determine the version number from the installation
-
Compare against vulnerable version rangeCompare your installed version against the affected range: any version less than or equal to 6.1.3 is vulnerableAffected if The installed version is 6.1.3 or lower (e.g., 6.1.2, 6.1.1, 6.0.0, etc.)
-
Verify PHP unserialize function usageReview plugin code for usage of PHP unserialize() function on user-supplied or external data. This is the entry point for the deserialization flaw. Check PHP files in the plugin directory for calls to unserialize() handling data from requests.Affected if The plugin code contains unserialize() calls processing untrusted input
You are affected if the WooCommerce Product Add-Ons plugin is installed with version 6.1.3 or lower and contains code that deserializes untrusted serialized data.
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 immediately, as deserialization vulnerabilities can be exploited to execute arbitrary code.
Fix this in Product Addons
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-32795 — 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-32795 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