CVE-2026-120846
WordPress Uncanny Automator plugin <= 7.7.1 - Broken Access Control vulnerability
Missing Authorization vulnerability in Uncanny Owl Uncanny Automator uncanny-automator allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Uncanny Automator: from n/a through 7.7.1.
Fixes and workarounds
Fix
Update the WordPress Uncanny Automator plugin to the latest available version (at least 8.0.0).
Source: CNA: PatchstackAffected products and versions
| Product | Versions | Authority |
|---|---|---|
| Uncanny Automator Uncanny Owl uncanny-automator
https://wordpress.org/plugins |
≥ 0; ≤ 7.7.1 (affected, custom); unaffected at 8.0.0
Other versions: unaffected |
CNA: Patchstack |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 3.1 / 5.3 medium |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N | CNA: Patchstack |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.