CVE-2026-2296
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 · uneditedThe Product Addons for Woocommerce – Product Options with Custom Fields plugin for WordPress is vulnerable to Code Injection in all versions up to, and including, 3.1.0. This is due to insufficient input validation of the 'operator' field in conditional logic rules within the evalConditions() function, which passes unsanitized user input directly to PHP's eval() function. This makes it possible for authenticated attackers, with Shop Manager-level access and above, to inject and execute arbitrary PHP code on the server via the conditional logic 'operator' parameter when saving addon form field rules.
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 confidenceThe Product Addons for Woocommerce plugin contains a code injection vulnerability in the evalConditions() function where the 'operator' field from conditional logic rules is passed directly to PHP's eval() without sanitization. This allows authenticated Shop Manager-level users to inject and execute arbitrary PHP code via the conditional logic operator parameter when saving addon form field rules.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- 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 Product Addons for WooCommerce plugin is installedCheck the WordPress plugins directory or WooCommerce plugins list for 'Product Addons for WooCommerce' or 'woocommerce-product-addons'Affected if The plugin is not installed, the vulnerability does not apply
-
Identify the installed plugin versionView the plugin header information via WordPress plugin admin page, or inspect the main plugin file (usually product-addons-for-woocommerce.php) for the 'Version' commentAffected if Version is at or before 3.1.0 (based on patched version mention of after 3.1.0)
-
Verify Shop Manager role exists in the WordPress installationNavigate to Users > Roles in WordPress admin, or use WP-CLI: wp role list | grep shop_managerAffected if The Shop Manager role does not exist, exploitation is not possible
-
Check if conditional logic rules are configured for any addonsNavigate to Products > Product Addons in WooCommerce, inspect addon field groups for 'Enable Conditional Logic' or similar settings; alternatively, query the wp_postmeta table for meta_key containing 'conditional_logic'Affected if Conditional logic is not enabled for any addon fields, the vulnerable evalConditions() function is not triggered
A user is affected if the Product Addons for WooCommerce plugin (version 3.1.0 or earlier) is installed, the Shop Manager role exists, and conditional logic rules with operator parameters are configured on addon form fields.
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 dataUpgrade to a patched version of the plugin (after 3.1.0) that properly sanitizes input before use in eval() or remove the eval() call entirely with safe expression evaluation; alternatively, restrict shop manager permissions until patched.
- Consultation3.0 h
- Implementation6.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2296 — 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-2026-2296 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