LiveActive security incident?Get immediate response
CVE Record

CVE-2023-23992: WordPress AutomatorWP Plugin <= 2.5.0 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in AutomatorWP plugin <= 2.5.0 leads to object delete.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-23992 affects the WordPress AutomatorWP plugin up to version 2.5.0. The flaw is a CSRF issue that can cause object deletion when a user is tricked into interacting with malicious content. Business impact is likely limited but can include disruption or loss of plugin-managed data.

Executive priority

Treat as a routine but time-bounded remediation item. Prioritize internet-facing WordPress sites and sites where AutomatorWP manages operational workflows or customer-facing automation.

Technical view

The source bundle identifies CWE-352 Cross-Site Request Forgery in AutomatorWP <= 2.5.0, with CVSS 3.1 score 5.4. The vector is network-accessible, low complexity, no attacker privileges, and requires user interaction. Reported impact is low availability impact via object delete.

Likely exposure

Exposure is limited to WordPress sites running AutomatorWP plugin version 2.5.0 or earlier. Risk is higher where privileged WordPress users stay logged in while browsing external content.

Exploitation context

The bundle does not show CISA KEV listing or any cited evidence of active exploitation. Exploitation requires user interaction, consistent with CSRF, and appears focused on causing deletion rather than confidentiality compromise.

Researcher notes

Evidence is sparse in the provided bundle. The record confirms CSRF leading to object delete, but does not provide request details, affected endpoints, fixed version, or vendor mitigation text. Avoid assuming exploitability beyond the CVSS and description.

Mitigation direction

  • Identify all WordPress sites using AutomatorWP.
  • Confirm whether AutomatorWP is version 2.5.0 or earlier.
  • Check AutomatorWP or Patchstack guidance for the corrected release.
  • Update the plugin according to vendor guidance.
  • Review backups for recoverability of deleted plugin-managed objects.

Validation and detection

  • Review WordPress plugin inventory for AutomatorWP installations.
  • Compare installed versions against the affected range: <= 2.5.0.
  • Check site logs for unexpected AutomatorWP object deletion activity.
  • Confirm the plugin update is present in staging before production rollout.
  • Verify critical AutomatorWP objects still exist after remediation.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

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 lookup
cve · low confidence lookup

CVE-2023-23992 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
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:N/A:L

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2023-23992Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AutomatorWPAutomatorWPautomatorwp, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

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.