CVE-2025-39600: WordPress Integration for WooCommerce and QuickBooks plugin <= 1.3.1 - Cross Site Request Forgery (CSRF) Vulnerability
Cross-Site Request Forgery (CSRF) vulnerability in CRM Perks Integration for WooCommerce and QuickBooks wp-woocommerce-quickbooks allows Cross Site Request Forgery.This issue affects Integration for WooCommerce and QuickBooks: from n/a through <= 1.3.1.
Security readout for executives and security teams
Plain-English summary
This is a medium-severity CSRF issue in the CRM Perks Integration for WooCommerce and QuickBooks WordPress plugin through version 1.3.1. A successful attack could trick a logged-in user into causing an unintended low-impact change. The supplied sources do not show active exploitation or a named fixed version.
Executive priority
Treat this as a normal-priority patch and exposure-management item, not an emergency. Prioritize sites where WooCommerce and QuickBooks synchronization affects revenue, invoicing, or operational records.
Technical view
CVE-2025-39600 is CWE-352 in wp-woocommerce-quickbooks. 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 limited to WordPress sites using CRM Perks Integration for WooCommerce and QuickBooks, package wp-woocommerce-quickbooks, at versions through 1.3.1. Sites not using this plugin are not indicated as affected by the supplied sources.
Exploitation context
The source bundle does not cite known exploitation, and KEV status is false. The CVSS vector indicates an attacker would need user interaction, consistent with CSRF. The sources do not describe the vulnerable action, proof of concept, or observed attacks.
Researcher notes
The public bundle gives severity, CVSS, CWE, affected plugin, and Patchstack reference, but not endpoint details, a fixed version, exploit maturity, or concrete impact beyond low integrity. Avoid assuming broader WooCommerce compromise from these sources alone.
Mitigation direction
Inventory WordPress sites for wp-woocommerce-quickbooks installations.
Check vendor, WordPress plugin, and Patchstack guidance for a fixed release.
Update the plugin if a fixed version is available from trusted channels.
Temporarily deactivate the plugin where business impact permits.
Review integration settings after remediation for unexpected changes.
Validation and detection
Confirm whether the plugin is installed on each WordPress site.
Record installed plugin versions and flag versions through 1.3.1.
Check change logs for unexpected WooCommerce or QuickBooks integration changes.
Verify remediation against vendor or Patchstack guidance before closure.
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.