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

> An attacker can access sensitive information without authorization in the Uncanny Automator WordPress plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jan 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-7jwp-9wj7-pp6x

## What is CVE-2023-52151?

CVE-2023-52151 is a medium-severity vulnerability in Uncanny Automator – Automate everything with the #1 no-code automation and integration plugin, published on 5 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2023-52151?

It affects 1 product.


Products: Uncannyowl Uncanny Automator.

## How do I fix CVE-2023-52151?

No fix has been published for CVE-2023-52151 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-52151 being exploited?

There is no known exploitation of CVE-2023-52151 in the wild and no public exploit code.

## Other vulnerabilities in Uncanny Automator – Automate everything with the #1 no-code automation and integration plugin

- [CVE-2025-3623](https://insights.sbomify.com/CVE-2025-3623/): Uncanny Automator <= 6.4.0.1 - Unauthenticated PHP Object Injection in automator_api_decode_message Function (critical 9.1)
- [CVE-2025-2075](https://insights.sbomify.com/CVE-2025-2075/): Uncanny Automator <= 6.3.0.2 - Missing Authorization to Authenticated (Subscriber+) Privilege Escalation (high 8.8)
- [CVE-2024-37117](https://insights.sbomify.com/CVE-2024-37117/): WordPress Uncanny Automator Pro plugin <= 5.3 - Reflected Cross Site Scripting (XSS) vulnerability (high 7.1)
- [CVE-2025-48133](https://insights.sbomify.com/CVE-2025-48133/): WordPress Uncanny Automator plugin <= 6.4.0.2 - Broken Access Control Vulnerability (medium 6.5)
- [CVE-2024-13838](https://insights.sbomify.com/CVE-2024-13838/): Server-side request forgery in Uncanny Automator – Easy Automation, Integration, Webhooks & Workflow Builder Plugin (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-52151 and fix it if it is affected.

What it is: CVE-2023-52151 is a medium-severity vulnerability in Uncanny Automator – Automate everything with the #1 no-code automation and integration plugin, published on 5 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-52151 in the wild and no public exploit code.

Affected product: Uncanny Automator – Automate everything with the #1 no-code automation and integration plugin. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-52151/ (Markdown: https://insights.sbomify.com/CVE-2023-52151/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-52151
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-52151
- OSV: https://osv.dev/vulnerability/CVE-2023-52151

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-52151/
Summaries are generated and may contain mistakes; the official description above is the record.