CVE-2026-82627

validated

GHSA-fg33-378f-xr8h ↗EUVD-2026-94658 ↗

check availablenot proven exploitable

cve.orgpublic pockev

uncannyowl Uncanny Automator – AI + Automation for WordPress | AI Agent, AI Page Builder, Free AI Usage Included <= 7.6.1.1

CWE-502 Deserialization of Untrusted Data

ETK-2026-928, permanent identifier

cvss7.5cna vendorCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

+2h21mTTV

57mAI analysis

Check if you are vulnerable

timeline

0 = trigger signal

trigger signal (cve.org) +0hcheck available+2h21magent stopped

+1h

+2h

description

Uncanny Automator for WordPress through version 7.6.1.1 is affected by PHP object injection. A user with Subscriber-level or greater access may be able to trigger object injection and potentially delete server files when a supported integration and a recipe storing attacker-controlled trigger metadata are present.

mitigation

Deactivate the plugin or disable affected integration recipes that retain user-controlled trigger metadata until a vendor-fixed release is confirmed. Restrict Subscriber and other low-privilege accounts to reduce exposure.

check

available

exploit

automation

deterministic

auth required

yes, low privileges

EPSS

0.27%17th percentile

agent run time

57m

cve.org record, t = 0

2026-10-08 01:26Z

Δ to public poc

–

Δ to kev

–

outcome

Check only, differential: the check fires on the vulnerable build and is silent on the patched one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

2026-10-08 01:26Z
cve_org: trigger signal, started the run
https://www.cve.org/CVERecord?id=CVE-2026-82627

this entry in the feed

GET /api/v1/feed/CVE-2026-82627

{
  "etk_id": "ETK-2026-928",
  "cve_id": "CVE-2026-82627",
  "display_id": "CVE-2026-82627",
  "ghsa_id": "GHSA-fg33-378f-xr8h",
  "euvd_id": "EUVD-2026-94658",
  "status": "published",
  "anchor_state": "anchored",
  "title": "PHP object injection in Uncanny Automator for WordPress",
  "summary": "Uncanny Automator for WordPress through version 7.6.1.1 is affected by PHP object injection. A user with Subscriber-level or greater access may be able to trigger object injection and potentially delete server files when a supported integration and a recipe storing attacker-controlled trigger metadata are present.",
  "mitigation": "Deactivate the plugin or disable affected integration recipes that retain user-controlled trigger metadata until a vendor-fixed release is confirmed. Restrict Subscriber and other low-privilege accounts to reduce exposure.",
  "vendor": "uncannyowl",
  "product": "Uncanny Automator – AI + Automation for WordPress | AI Agent, AI Page Builder, Free AI Usage Included",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 7.6.1.1"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Uncanny Automator – AI + Automation for WordPress | AI Agent, AI Page Builder, Free AI Usage Included",
      "purl": null
    }
  ],
  "cwes": [
    502
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0027,
  "epss_percentile": 0.1734,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 56.74877453333333,
  "t0_at": "2026-10-08T01:26:38.471000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-08T03:47:45.232444+00:00",
      "days": 0.09799492412037036,
      "is_lower_bound": false,
      "measured_at": "2026-10-08T01:26:38.471000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-08T01:26:38.471000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-08T01:26:38.471000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-82627"
    }
  }
}

published 2026-10-08 02:50Z
last change 2026-10-21 15:37Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.