CVE-2026-22333
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 YITHEMES YITH WooCommerce Compare yith-woocommerce-compare allows Object Injection.This issue affects YITH WooCommerce Compare: from n/a through <= 3.6.0.
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 confidenceThis is a PHP Object Injection vulnerability in the YITH WooCommerce Compare plugin caused by deserializing untrusted data (likely via PHP's unserialize() function). An attacker can craft malicious serialized PHP objects that, when deserialized, may execute arbitrary code, write files, or perform other harmful operations depending on available gadget chains in the application and server environment.
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.
-
Verify YITH WooCommerce Compare plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'YITH WooCommerce Compare' or check the file system at wp-content/plugins/yith-woocommerce-compare for the main plugin file (usually index.php or main class file) and read the version header commentAffected if The plugin is installed and active in WordPress
-
Confirm the installed plugin versionOpen the main plugin file (e.g., yith-woocommerce-compare.php or class-yith-woocommerce-compare.php) and locate the 'Version:' header in the plugin comment block at the top, or check the readme.txt file for the stable tagAffected if The installed version matches or precedes the last known vulnerable version (compare against vendor release notes for the patched version)
-
Identify unsafe deserialization in plugin codeSearch plugin PHP files for calls to unserialize() function - use grep or a file search: grep -r "unserialize" wp-content/plugins/yith-woocommerce-compare/Affected if The plugin code contains unserialize() calls that process data
-
Check if untrusted input reaches the deserializationExamine the code around any unserialize() calls found - trace back to see if the data being deserialized comes from $_GET, $_POST, $_REQUEST, cookies, or database fields that could be controlled by external usersAffected if User-supplied data (from HTTP requests, database, or other external sources) is passed directly to unserialize() without prior sanitization
You are affected if YITH WooCommerce Compare plugin is installed, contains unserialize() calls processing external input, and your installed version is before the vendor-patched release.
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 to a patched version of YITH WooCommerce Compare if available. If no patch exists, replace unsafe deserialization (unserialize()) with safer alternatives like JSON decoding and implement strict input validation on all data passed to deserialization functions.
- 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-22333 — 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-22333 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