LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22333: WordPress YITH WooCommerce Compare plugin <= 3.6.0 - Deserialization of untrusted data vulnerability

Deserialization 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.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-22333 affects the WordPress YITH WooCommerce Compare plugin through version 3.6.0. It is a high-severity unsafe deserialization issue that could allow object injection. The CVSS data indicates exploitation requires high privileges, reducing broad internet risk, but successful abuse could affect confidentiality, integrity, and availability.

Executive priority

Prioritize review for e-commerce sites using this plugin, especially where many administrators or third parties have privileged access. Treat as high priority, but not emergency internet-wide exploitation based on current supplied evidence.

Technical view

The issue is CWE-502, deserialization of untrusted data, in YITHEMES YITH WooCommerce Compare <= 3.6.0. CVSS 3.1 is 7.2 with network attack vector, low complexity, high privileges required, no user interaction, unchanged scope, and high CIA impact. Public source data does not identify a fixed version or specific mitigations.

Likely exposure

WordPress and WooCommerce environments using YITH WooCommerce Compare version 3.6.0 or earlier are potentially exposed. Sites without this plugin, or running versions outside the affected range per vendor confirmation, are not indicated as affected by the provided sources.

Exploitation context

No active exploitation is stated in the provided sources, and the CVE is not marked KEV. The CVSS privilege requirement is high, suggesting an attacker likely needs a highly privileged WordPress account or equivalent access before exploitation is practical.

Researcher notes

The public record establishes affected range, CWE, and CVSS, but does not provide patch version, root-cause details, proof of exploitation, or exploit prerequisites beyond PR:H. Avoid assuming unauthenticated exploitation. Validate against vendor/Patchstack updates before closing remediation.

Mitigation direction

  • Inventory WordPress sites for YITH WooCommerce Compare installations.
  • Check vendor and Patchstack guidance for a fixed version or official workaround.
  • Update the plugin if a fixed release is available.
  • Disable or remove the plugin where business use is not required.
  • Restrict high-privilege WordPress accounts to trusted users only.
  • Monitor privileged account activity and unexpected plugin behavior.

Validation and detection

  • Confirm whether the plugin is installed and enabled on each WordPress site.
  • Record the installed plugin version and compare it to <= 3.6.0.
  • Verify vendor or Patchstack advisory status for remediation details.
  • Review administrator and shop-manager account access for unnecessary privileges.
  • Check security monitoring for unusual privileged WordPress activity.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-502: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-22333 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H1.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.2High
CVSS 3.1 vector shape for CVE-2026-22333Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
YITHEMESYITH WooCommerce Compareyith-woocommerce-compare, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-502 · source CWE mapping

Deserialization of Untrusted Data

Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.