Security readout for executives and security teams
Plain-English summary
CVE-2023-47237 affects the WordPress Auto Publish for Google My Business plugin through version 3.7. The issue is CSRF: an attacker could trick a logged-in site user into making unintended changes. The CVSS score is high, but the provided sources do not show active exploitation.
Executive priority
Prioritize remediation on public WordPress sites that use this plugin, especially business-critical sites with multiple administrators. Treat as high risk, but not as known exploited from the provided evidence.
Technical view
The CVE describes CWE-352 Cross-Site Request Forgery in Martin Gibson Auto Publish for Google My Business, package wp-google-my-business-auto-publish, affecting versions <= 3.7. CVSS 3.1 is 8.8 with network attack vector, low complexity, no attacker privileges, and required user interaction.
Likely exposure
Exposure is limited to WordPress sites with Auto Publish for Google My Business installed at version 3.7 or earlier. Sites without this plugin are not affected based on the supplied sources.
Exploitation context
The source bundle does not cite CISA KEV listing or active exploitation. The CVSS vector requires user interaction, consistent with CSRF risk against an authenticated WordPress user.
Researcher notes
The public bundle confirms CSRF class, affected plugin, CVSS score, and <=3.7 affected range. It does not provide endpoint details, exploit proof, or a specific fixed version, so validation should stay version- and vendor-guidance based.
Mitigation direction
- Inventory WordPress sites for wp-google-my-business-auto-publish plugin usage.
- Update the plugin following vendor or Patchstack guidance.
- Disable or remove the plugin if no maintained fixed release is available.
- Restrict WordPress administrator access to trusted users.
- Review recent admin activity for unexpected plugin or posting changes.
Validation and detection
- Check installed plugin version on each WordPress site.
- Confirm whether version is 3.7 or earlier.
- Verify the plugin is updated, disabled, or removed.
- Review WordPress logs for suspicious admin-triggered changes.
- Confirm no unsupported fork or renamed copy remains installed.
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-47237 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
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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:H/I:H/A:H2.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.