Security readout for executives and security teams
Plain-English summary
This vulnerability affects the WordPress YITH WooCommerce Compare plugin through version 2.37.0. It is a CSRF issue, meaning an attacker may be able to trick a logged-in user into causing an unintended change. The documented impact is limited to integrity, not data theft or service outage.
Executive priority
Treat this as a moderate-priority WordPress plugin hygiene issue. It should be remediated during the next normal maintenance window, faster for public e-commerce sites with many administrators or high business impact.
Technical view
CVE-2024-32699 is CWE-352 Cross-Site Request Forgery in yith-woocommerce-compare through 2.37.0. CVSS 3.1 is 4.3: network reachable, low complexity, no attacker privileges, user interaction required, unchanged scope, low integrity impact, no confidentiality or availability impact.
Likely exposure
Exposure is likely limited to WordPress/WooCommerce sites running YITH WooCommerce Compare version 2.37.0 or earlier. The source bundle does not identify affected endpoints, required victim role, or specific state-changing action.
Exploitation context
The CVE is not listed as CISA KEV in the provided bundle, and no cited source states active exploitation. Successful exploitation requires user interaction, consistent with CSRF, likely by inducing a logged-in user to trigger an unintended request.
Researcher notes
The public metadata confirms vulnerability class, affected product, affected version ceiling, and CVSS vector. It does not describe the vulnerable action, nonce failure location, proof of concept, fixed version, or exploitation in the wild.
Mitigation direction
Inventory WordPress sites for YITH WooCommerce Compare versions 2.37.0 or earlier.
Check YITHEMES, WordPress plugin, or Patchstack guidance for a vendor-confirmed fixed version.
Update or remove affected plugin installations following vendor guidance.
Reduce CSRF exposure by avoiding untrusted links while logged into WordPress admin.
Consider temporarily disabling the plugin on high-risk stores if no fix is available.
Validation and detection
Confirm whether yith-woocommerce-compare is installed on each WordPress site.
Record the installed plugin version and compare it with the affected range through 2.37.0.
Review vendor or Patchstack advisories for fixed-release or mitigation details.
Verify remediation by confirming the plugin is updated, removed, or otherwise covered by vendor guidance.
Check logs only for suspicious admin-side state changes; sources do not provide exploit indicators.
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-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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.
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.
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-352 · source CWE mapping
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.