VulnerabilityPublished 28 Oct 2026

CVE-2026-104694: Thrive Automator (WordPress plugin) · SQL Injection

Affects Thrive Automator (WordPress plugin)Source CVE Database V5

Not known to be exploited : upgrade to 11.2 soon.

Data as of 28 Oct 2026, 06: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.

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

Upgrade the Thrive Automator plugin to version 11.2 or later, where this SQL injection vulnerability has been fixed. No additional mitigation steps are required if the plugin is updated.

Description

A SQL injection vulnerability exists in the Thrive Automator WordPress plugin versions before 11.2. The flaw arises because the plugin does not properly sanitize and escape a parameter's array key before using it in a SQL query. This allows authenticated users with editor-level access to perform blind SQL injection attacks. The issue is fixed in version 11.2.

Impact

Authenticated users 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 at this time.

Summary

The Thrive Automator WordPress plugin prior to version 11.2 improperly handles input by failing to sanitize and escape a parameter's array key before incorporating it into a SQL query. This vulnerability enables authenticated attackers with editor privileges to conduct blind SQL injection attacks, potentially compromising the database. The vulnerability is tracked as CVE-2026-104694 and is classified under CWE-89 (SQL Injection). A fix is available in version 11.2.

CWE-89Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #2OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Parameterization
If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.
Architecture and Design · Operation · Environment Hardening
Run your code using the lowest privileges that are required to accomplish the necessary tasks. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment.
OWASP Cheat Sheets
Query Parameterization (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
XML Security (opens in a new tab)
XML External Entity Prevention (opens in a new tab)
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.4 (opens in a new tab)
V5.3.5 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
Command Line Execution through SQL Injection (opens in a new tab)
Object Relational Mapping Injection (opens in a new tab)
SQL Injection through SOAP Parameter Tampering (opens in a new tab)
Expanding Control over the Operating System from the Database (opens in a new tab)
SQL Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

wpscan.com/vulnerability/ad8f60bb-ee1d-4472-92fa-e4e22fed1471/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Oct 2026, 06:28 UTC

WeaknessesCWE-89

Technical details

References

Community reviews

Related threats