LiveActive security incident?Get immediate response
CVE Record

CVE-2023-52151: WordPress Uncanny Automator Plugin <= 5.1.0.2 is vulnerable to Sensitive Data Exposure

Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Uncanny Automator, Uncanny Owl Uncanny Automator – Automate everything with the #1 no-code automation and integration plugin.This issue affects Uncanny Automator – Automate everything with the #1 no-code automation and integration plugin: from n/a through 5.1.0.2.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-52151 is a WordPress plugin issue where Uncanny Automator through 5.1.0.2 may expose sensitive information through log files. The known impact is limited to confidentiality, but exposure is unauthenticated over the network, so public WordPress sites using this plugin should be reviewed promptly.

Executive priority

Treat this as a moderate-priority WordPress exposure issue. It is not described as system takeover, but unauthenticated information disclosure can leak operational or integration data and should be remediated during the next security maintenance window.

Technical view

The CVE describes CWE-200 sensitive information exposure in the Uncanny Automator WordPress plugin, package name uncanny-automator, affecting versions through 5.1.0.2. CVSS 3.1 is 5.3: network reachable, low complexity, no privileges, no user interaction, unchanged scope, low confidentiality impact, no integrity or availability impact.

Likely exposure

Exposure is most likely on WordPress sites running Uncanny Automator at version 5.1.0.2 or earlier, especially where plugin log files are reachable without authentication. The supplied sources do not identify specific exposed data types or paths.

Exploitation context

The source bundle does not show CISA KEV listing or other cited evidence of active exploitation. The CVSS vector indicates unauthenticated remote access is possible, but no exploit procedure, payload, or real-world exploitation evidence is provided.

Researcher notes

Evidence is limited to the CVE metadata and Patchstack database reference. The vulnerability is described as sensitive data exposure via log file, but the provided sources do not specify exact log locations, fixed version, exposed fields, or exploitation in the wild.

Mitigation direction

  • Inventory WordPress sites using the Uncanny Automator plugin.
  • Upgrade beyond affected versions according to vendor or plugin repository guidance.
  • Restrict public access to plugin log files and operational logs.
  • Review exposed logs for sensitive data and rotate affected secrets if found.
  • Monitor vendor and Patchstack advisories for confirmed fixed versions.

Validation and detection

  • Confirm whether uncanny-automator is installed on each WordPress site.
  • Record installed plugin versions and flag 5.1.0.2 or earlier.
  • Check whether plugin logs are accessible without authentication.
  • Review web and application logs for unusual unauthenticated log-file access.
  • Document whether sensitive information appeared in exposed log content.
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-200: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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-52151 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.3 (3.1)
Known Exploited
No
Published

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

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.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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
Uncanny Automator, Uncanny OwlUncanny Automator – Automate everything with the #1 no-code automation and integration pluginuncanny-automator, n/aunaffected
Weakness

CWE details

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

CWE-200 · source CWE mapping

Exposure of Sensitive Information to an Unauthorized Actor

Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.