Security readout for executives and security teams
Plain-English summary
CVE-2023-37974 is a medium-severity CSRF issue in the WordPress WP Social AutoConnect plugin, also identified as wp-fb-autoconnect, through version 4.6.1. A successful attack could cause limited integrity or availability impact if a targeted user is tricked into interacting with attacker-controlled content.
Executive priority
Treat as a moderate WordPress hygiene issue, not an emergency based on current evidence. Prioritize quick inventory and removal or upgrade where the plugin is present, especially on externally managed or business-critical WordPress sites.
Technical view
The issue is CWE-352 Cross-Site Request Forgery in Justin Klein WP Social AutoConnect <= 4.6.1. CVSS 3.1 is 5.4 with network attack vector, low complexity, no attacker privileges, required user interaction, unchanged scope, no confidentiality impact, and low integrity and availability impact.
Likely exposure
Exposure is limited to WordPress sites with the WP Social AutoConnect/wp-fb-autoconnect plugin installed at version 4.6.1 or earlier. The bundle does not identify affected CPEs or a fixed version, so inventory confirmation is necessary.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The CVSS vector requires user interaction. Because this is CSRF, realistic risk depends on logged-in user context and what plugin action can be forced, which the bundle does not specify.
Researcher notes
Evidence is thin: the bundle identifies CSRF, affected plugin, version ceiling, CVSS, and Patchstack reference, but not the vulnerable endpoint, required victim role, fixed release, or exploit observations. Avoid claiming exploitability beyond CSRF with required user interaction.
Mitigation direction
- Inventory WordPress sites for wp-fb-autoconnect or WP Social AutoConnect installations.
- Check vendor, WordPress plugin, and Patchstack guidance for a fixed or supported version.
- Upgrade if an official fixed version is available from trusted sources.
- Disable or remove the plugin where no supported fix exists.
- Limit administrative access and use routine WordPress anti-CSRF hardening practices.
Validation and detection
- Confirm installed plugin slug and version on each WordPress site.
- Compare findings against CVE and Patchstack records for version scope.
- Review administrative audit logs for unexpected plugin configuration changes.
- Document whether the plugin is business-required or can be removed.
- Track remediation status separately for each affected WordPress instance.
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-37974 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
- Medium
- CVSS
- 5.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
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 vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L2.82.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
Source materials
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.