Security readout for executives and security teams
Plain-English summary
This issue affects the WooCommerce Google Sheet Connector WordPress plugin before 1.3.6. A malicious site could trick a logged-in administrator into changing the plugin Access Code, potentially disrupting or redirecting the connector’s integration workflow.
Executive priority
Prioritize remediation on WooCommerce sites that rely on this connector for business workflows. The issue is not rated with CVSS and active exploitation is not confirmed, but admin-level CSRF can still affect operational integrity.
Technical view
The plugin update path for the Access Code lacked a CSRF check before version 1.3.6. The impact depends on an authenticated administrator’s browser performing an unintended state-changing action. The sources do not provide CVSS scoring or broader product impact details.
Likely exposure
Exposure is likely limited to WordPress/WooCommerce sites running WooCommerce Google Sheet Connector versions before 1.3.6, especially where administrators remain logged in while browsing external content.
Exploitation context
The source bundle lists a WPScan entry tagged as exploit, but CISA KEV is false and no source states active exploitation. Treat as plausible web-admin social-engineering risk, not confirmed in-the-wild exploitation.
Researcher notes
Evidence is sparse: the CVE description identifies missing CSRF protection for Access Code updates before 1.3.6, but provides no CVSS vector, exploit details, or confirmed exploitation. Validate version and configuration state rather than assuming compromise.
Mitigation direction
- Upgrade WooCommerce Google Sheet Connector to version 1.3.6 or later.
- Check vendor and WPScan guidance for any additional remediation notes.
- Review and rotate the plugin Access Code if unauthorized changes are suspected.
- Limit WordPress administrator access to trusted users only.
- Encourage admins to log out before visiting untrusted links.
Validation and detection
- Inventory WordPress sites for WooCommerce Google Sheet Connector installations.
- Confirm the installed plugin version is 1.3.6 or later.
- Review plugin settings for unexpected Access Code changes.
- Check administrative audit logs around plugin configuration changes.
- Confirm change-control records match any recent Access Code updates.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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.
Open ATT&CK lookupCVE-2023-2329 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://wpscan.com/vulnerability/6e58f099-e8d6-49e4-9f02-d6a556c5b1d2CVE reference · exploit, vdb-entry
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.