CVE-2026-118239VulnerabilityPublished 6 Nov 2026

The AutomatorWP WordPress plugin before 6.0.7 does not check that the user completing its Zoom and AWeber integration

Source GCVE Database

Compare

Authoritative record:CVE-2026-118239· High

Not known to be exploited : upgrade to 6.0.7 soon.

Data as of 6 Nov 2026, 07:21 UTC

Severity

High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Patch: Available – fixed in 6.0.7

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-gpq2-qwv8-rj79

What to do

Upgrade AutomatorWP (WordPress plugin) to 6.0.7.

Affected software

Product	Affected	Fixed in
AutomatorWP	Affected <6.0.7	Fixed in 6.0.7

AI-suggested

If you cannot patch yet, restrict access to integration configuration interfaces and monitor for unauthorized changes. Avoid exposing OAuth client identifiers publicly.

Description

The AutomatorWP WordPress plugin versions before 6.0.7 contain a vulnerability where it does not verify that the user completing Zoom and AWeber integration connections is authorized. This flaw allows unauthenticated attackers to replace stored integration credentials with their own, redirecting data sent to these services into accounts they control. Exploitation requires the integration to be already connected and knowledge of the site's OAuth client identifier.

Impact

An attacker can hijack the Zoom and AWeber integration credentials by replacing them with their own, potentially diverting sensitive data sent from the site to attacker-controlled accounts. This compromises the confidentiality and integrity of data exchanged via these integrations. The attack requires no authentication but does require prior connection of the integrations and knowledge of the OAuth client identifier.

Summary

AutomatorWP versions prior to 6.0.7 fail to check user authorization when completing Zoom and AWeber integration connections. This lack of verification enables unauthenticated attackers to overwrite stored integration credentials, thereby diverting data intended for the legitimate service accounts to attacker-controlled accounts. Successful exploitation depends on the integration being active and the attacker knowing the site's OAuth client identifier.

References

Community reviews

Loading reviews…