CVE-2026-104694

Thrive Automator < 11.2 - Editor+ Blind SQLi via 'additional' Parameter

Published Oct 28, 2026 CVSS 3.1 · 6.8 Medium EPSS < 1% KEV · Not listed
Description
The Thrive Automator WordPress plugin before 11.2 does not properly sanitize and escape a parameter's array key before using it in a SQL query, allowing authenticated attackers with editor-level access to perform blind SQL injection attacks.

Analysis

AI-generated

Technical impact

The Thrive Automator WordPress plugin before version 11.2 contains a flaw in which an array key supplied via the 'additional' parameter is not properly sanitized or escaped before being placed into a SQL query. This weakness allows an authenticated user with editor‑level privileges to submit a malicious payload that is executed by the database engine, resulting in a blind SQL injection that can read or alter the WordPress database. The impact therefore spans data confidentiality and integrity for all content stored in the site.

Affected Systems

Any WordPress installation that hosts the Thrive Automator plugin with a version older than 11.2 is vulnerable. The flaw is triggered only when a logged‑in user possesses editor‑level permissions and submits the vulnerable 'additional' parameter. Sites that do not have Thrive Automator, or that run 11.2 or later, are not affected.

Risk and Exploitability

Exploitation requires an authenticated editor account, which narrows the available attack surface to sites where such roles exist. The EPSS score of less than 1% and absence from the CISA KEV catalog suggest a low likelihood of widespread targeting. Nonetheless, the CVSS score of 6.8 indicates moderate severity, and a successful attack could grant the attacker read or write capability over the WordPress database, posing a high impact to data confidentiality and integrity.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update Thrive Automator to version 11.2 or later.
  • Restrict editor permissions to trusted users only, or remove unused editor roles.
  • Monitor database logs for unauthorized SQL queries and apply general database hardening practices.

Generated by OpenCVE AI on October 28, 2026 at 22:29 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Wordpress-extensions
Wordpress-extensions thrive Automator
Vendors & Products Wordpress-extensions
Wordpress-extensions thrive Automator
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-20
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 6.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N'}

Type Values Removed Values Added
Weaknesses CWE-20
CWE-89
Type Values Removed Values Added
Description The Thrive Automator WordPress plugin before 11.2 does not properly sanitize and escape a parameter's array key before using it in a SQL query, allowing authenticated attackers with editor-level access to perform blind SQL injection attacks.
Title Thrive Automator < 11.2 - Editor+ Blind SQLi via 'additional' Parameter
References
Weaknesses
  • CWE-89

    Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Sources

Status
PUBLISHED
Assigner
WPScan
Published
Updated
Oct 28, 2026, 5:58 PM
Reserved
Oct 2, 2026, 8:46 AM
Status
Deferred
Published
Oct 28, 2026, 6:16 AM
Modified
Oct 28, 2026, 6:17 PM