Quick answers
- Is CVE-2026-121472 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-121472 being exploited in the wild.
- How severe is CVE-2026-121472?
- Informational severity, published 11 November 2026.
- Which products and versions are affected?
- AutomatorWP before 6.0.8.
- Is there a fix for CVE-2026-121472?
- Yes: fixed in 6.0.8. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-121472 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-121472?
- 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.
How to fix
- Fixed in: 6.0.8
Technical details
The plugin fails to bind OAuth completion requests to the administrator session that initiated them, allowing CSRF attacks to replace stored integration credentials. Exploitation requires an already-connected integration and knowledge of the site's OAuth client ID. An attacker can trick a logged-in admin into visiting a malicious page that replaces Zoom or AWeber credentials, diverting subsequent data flows to the attacker's accounts.
Affected products
- AutomatorWP AutomatorWP before 6.0.8
Timeline
- 2026-11-09: disclosed
- 2026-11-11: advisory