Security readout for executives and security teams
Plain-English summary
This is a medium-severity CSRF issue in the WordPress Automated Editor plugin. If an authenticated site user can be tricked into taking an unintended action, the site may suffer limited integrity or availability impact. The sources do not show active exploitation or a confirmed fixed version.
Executive priority
Treat this as a targeted WordPress plugin hygiene issue, not an emergency. Prioritize sites that are public-facing, business-critical, or administered by many users, and resolve through normal vulnerability management once vendor guidance is confirmed.
Technical view
CVE-2023-45276 is CWE-352 affecting automatededitor.com Automated Editor, with the title and description identifying WordPress plugin versions <= 1.3. CVSS 3.1 is 5.4, network reachable, low complexity, no attacker privileges, user interaction required, with low integrity and availability impact.
Likely exposure
Exposure is likely limited to WordPress sites using the Automated Editor plugin, especially installations at version 1.3 or earlier. The source bundle lists package name automated-editor but affected version metadata is sparse, so asset inventory must confirm actual deployment.
Exploitation context
The CVE is not listed as CISA KEV in the source bundle. The available evidence supports CSRF risk requiring user interaction, but does not support claims of public exploitation, weaponized exploit availability, or broad campaign activity.
Researcher notes
Evidence is thin beyond the CVE record and Patchstack entry. Do not infer affected forks, exploit maturity, or a fixed release from the provided bundle. The CVSS vector indicates CSRF with user interaction and limited integrity and availability impact.
Mitigation direction
- Inventory WordPress sites for the automated-editor plugin and record installed versions.
- Check vendor and Patchstack guidance for a fixed version or official workaround.
- Update only to a vendor-confirmed fixed release when available.
- Disable or remove the plugin where it is not required.
- Limit administrative sessions and review existing WordPress CSRF defenses.
Validation and detection
- Compare installed plugin versions against the advisory's <= 1.3 scope.
- Confirm whether the plugin is active on public or business-critical WordPress sites.
- Review WordPress audit logs for unexpected Automated Editor-related changes.
- Verify remediation against vendor or Patchstack guidance before closure.
- Document uncertainty where version or fix information cannot be confirmed.
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-45276 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.