Quick answers
- Is CVE-2026-78266 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-78266 being exploited in the wild.
- How severe is CVE-2026-78266?
- Medium severity, with a CVSS score of 6.5, published 24 August 2026.
- Which products and versions are affected?
- AutomatorWP <= 5.8.3.
- Is there a fix for CVE-2026-78266?
- A patch was published on 2026-08-24: Version 5.8.4 or later Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-78266 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-78266?
- Check whether you run AutomatorWP at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This is a broken access control vulnerability (CWE-639) in AutomatorWP versions up to and including 5.8.3. The vulnerability allows users with the subscriber role to bypass authorization checks and access functionality or data restricted to higher-privilege roles. The attack vector is network-based and requires the attacker to possess a valid subscriber account on the affected WordPress installation. An authenticated attacker can exploit this to view sensitive information or perform unauthorized administrative actions. The vulnerability is patched in version 5.8.4 and later.
Affected products
- AutomatorWP AutomatorWP <= 5.8.3
Timeline
- 2026-08-24: disclosed
- 2026-08-24: patched: Version 5.8.4 or later
- 2026-08-24: advisory: Patchstack advisory published