CVE-2026-104694VulnerabilityPublished 28 Oct 2026

The Thrive Automator WordPress plugin before 11.2 does not properly sanitize and escape a parameter's array key before

Source GCVE Database

Authoritative record:CVE-2026-104694· High

Not known to be exploited : upgrade to 11.2 soon.

Data as of 28 Oct 2026, 07:28 UTC

Severity

High

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

Patch: Available – fixed in 11.2

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, 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-v8w6-566x-2cm3

What to do

Upgrade Thrive Automator (WordPress plugin) to 11.2.

Affected software

Product	Affected	Fixed in
Thrive Automator	Affected <11.2	Fixed in 11.2

AI-suggested

Users should upgrade the Thrive Automator WordPress plugin to version 11.2 or later where this vulnerability is fixed. Since the vulnerability affects versions before 11.2, applying this official fix will remediate the issue.

Description

The Thrive Automator WordPress plugin versions before 11.2 contain a vulnerability where a parameter's array key is not properly sanitized and escaped before being used in a SQL query. This flaw allows authenticated users with editor-level privileges to perform blind SQL injection attacks.

Impact

Authenticated attackers with editor-level access can exploit this vulnerability to perform blind SQL injection attacks. This could lead to unauthorized data access or manipulation within the WordPress database. There is no indication of active exploitation in the wild or public exploit code at this time.

Summary

The Thrive Automator WordPress plugin prior to version 11.2 fails to properly sanitize and escape a parameter's array key before incorporating it into a SQL query. This vulnerability enables attackers who have authenticated editor-level access to execute blind SQL injection attacks against the underlying database, potentially compromising data confidentiality and integrity.

References

Community reviews

Loading reviews…