Security readout for executives and security teams
Plain-English summary
A WordPress site using Caldera Forms Google Sheets Connector before 1.3 could let a tricked, logged-in administrator unknowingly change the plugin access code. This is not reported as actively exploited in the supplied sources, but it can affect integrity of the Google Sheets form integration.
Executive priority
Treat as a targeted remediation item for affected WordPress sites, not a broad emergency. Prioritize if the plugin handles business-critical form submissions or sensitive data flows into Google Sheets.
Technical view
CVE-2023-2330 is a CWE-352 CSRF issue in Caldera Forms Google Sheets Connector before 1.3. The vulnerable settings path lacks a CSRF check when updating the Access Code, allowing an attacker to induce an authenticated admin browser to set an arbitrary value.
Likely exposure
Exposure appears limited to WordPress sites with Caldera Forms Google Sheets Connector installed below version 1.3 and an administrator who can be induced to perform a forged request.
Exploitation context
The source describes a CSRF condition and WPScan tags exploit availability, but the bundle does not show CISA KEV listing or confirmed active exploitation. It requires a logged-in admin context.
Researcher notes
Evidence is narrow: the bundle identifies the vulnerable plugin, affected versions before 1.3, CWE-352, and the access-code update behavior. No CVSS vector, vendor advisory detail, or active exploitation confirmation is provided.
Mitigation direction
- Inventory WordPress sites for Caldera Forms Google Sheets Connector.
- Confirm the plugin is version 1.3 or later where available.
- If still below 1.3, follow vendor or WPScan remediation guidance.
- Limit administrator sessions and access until the plugin is remediated.
- Review connected Google Sheets integration credentials after remediation.
Validation and detection
- Check installed plugin version on each WordPress instance.
- Verify the access code update path has CSRF protection.
- Review recent plugin settings changes for unexpected access code updates.
- Confirm only trusted administrators can manage plugin settings.
- Re-test after upgrade or configuration change.
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-2330 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/fa8ccdd0-7b23-4b12-9aa9-4b29d47256b8CVE 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.