Quick answers
- Is CVE-2026-118239 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118239 being exploited in the wild.
- How severe is CVE-2026-118239?
- Informational severity, published 6 November 2026.
- Which products and versions are affected?
- AutomatorWP before 6.0.7.
- Is there a fix for CVE-2026-118239?
- Yes: fixed in 6.0.7. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-118239 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-118239?
- 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.7
Technical details
The plugin fails to verify that the user completing Zoom and AWeber OAuth integration callbacks has authorization to do so, leading to broken access control (CWE-284). An unauthenticated attacker can intercept or craft a callback request to replace the stored OAuth credentials, provided they know the site's OAuth client identifier and the integration was previously set up. This allows credential replacement and account takeover of the integrations.
Affected products
- AutomatorWP AutomatorWP before 6.0.7
Timeline
- 2026-11-04: disclosed
- 2026-11-06: advisory