YITH WooCommerce Compare <= 3.6.0 - Authenticated (Admin+) PHP Object Injection
Strategic Overview
- Status
- Patched in 3.7.0
- Affected Plugin
- YITH WooCommerce Compare
- Affected Version
<= 3.6.0- CVSS
- 6.6Medium
- Weakness type
- CWE-502 · Deserialization of Untrusted Data
- CVE
CVE-2026-22333
At a glance
CVE-2026-22333 is a medium-severity Deserialization of Untrusted Data vulnerability in the YITH WooCommerce Compare WordPress plugin, affecting versions <= 3.6.0. It carries a CVSS score of 6.6 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Admin level or above. The issue is fixed in version 3.7.0; sites on affected versions should update now. Disclosed August 2025, reported by Drew Webber (mcdruid).
Vulnerability Overview
The YITH WooCommerce Compare plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 3.6.0 via deserialization of untrusted input. This makes it possible for authenticated attackers, with Administrator-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable software, which means this vulnerability has no impact unless another plugin or theme containing a POP chain is installed on the site. If a POP chain is present via an additional plugin or theme installed on the target system, it may allow the attacker to perform actions like delete arbitrary files, retrieve sensitive data, or execute code depending on the POP chain present.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-502: Deserialization of Untrusted Data
Reaching this weakness in YITH WooCommerce Compare <= 3.6.0 takes an account at Admin level or above. Deserialization of untrusted data means the application reconstructs objects from input a caller controls, letting the attacker choose which classes get instantiated and what their properties hold.
A workable chain turns deserialization into file writes, deletions or code execution, depending on what the loaded classes do in their magic methods. For YITH WooCommerce Compare the fix is 3.7.0: builds <= 3.6.0 are affected, anything from 3.7.0 onward is not.
Remediation
Update to version 3.7.0, or a newer patched version
How does WordSec protect against this?
An attacker needs Admin access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: YITH WooCommerce Compare 3.7.0 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in YITH WooCommerce Compare
- 7.1YITH plugins by YITHEMES <= (Various Versions) Missing Authorization
- 4.3CVE-2024-32699: YITH WooCommerce Compare <= 2.37.0 CSRF
CVE-2024-32699 - 4.3CVE-2022-44630: YITH plugins by YITHEMES <= (Various Versions) CSRF
CVE-2022-44630 - 4.3CVE-2019-16251: YIT Plugin Framework <= 3.3.8 Settings Change
CVE-2019-16251
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C