# CVE-2026-82627: Deserialization in Uncanny Automator – AI + Automation for WordPress | AI Agent, AI Page Builder, Free AI Usage Included

> Authenticated attackers can delete arbitrary files via PHP object injection if specific third-party integrations are configured.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Oct 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-fg33-378f-xr8h

## What is CVE-2026-82627?

CVE-2026-82627 is a high-severity unsafe deserialization vulnerability in uncannyowl Uncanny Automator – AI + Automation for WordPress | AI Agent, AI Page Builder, Free AI Usage Included, published on 8 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Uncanny Automator – AI + Automation for WordPress | AI Agent, AI Page Builder, Free AI Usage Included plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 7.6.1.1 via deserialization of untrusted input. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject a PHP Object when a third-party integration plugin (such as PeepSo,  MailPoet, WPForms, etc) is installed and a recipe is configured that stores attacker-controlled data as trigger meta. The additional presence of a POP chain within Uncanny Automator allows attackers to delete arbitrary files on the server.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2026-82627?


## How do I fix CVE-2026-82627?

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

## Is CVE-2026-82627 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-82627 and fix it if it is affected.

What it is: CVE-2026-82627 is a high-severity unsafe deserialization vulnerability in uncannyowl Uncanny Automator – AI + Automation for WordPress | AI Agent, AI Page Builder, Free AI Usage Included, published on 8 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-82627 in the wild and no public exploit code.

Affected product: uncannyowl Uncanny Automator – AI + Automation for WordPress | AI Agent, AI Page Builder, Free AI Usage Included. 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-2026-82627/ (Markdown: https://insights.sbomify.com/CVE-2026-82627/index.md)
```

## Sources

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

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