CVE-2026-104694EUVD-2026-111700GHSA-V8W6-566X-2CM3
Thrive Automator < 11.2 - Editor+ Blind SQLi via 'additional' Parameter
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 11.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
The Thrive Automator plugin for WordPress is affected, allowing users with editor-level access to run blind SQL injection attacks through a parameter that is not properly sanitized. Successful exploitation could let an attacker read or manipulate data in the website's database.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original 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.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Unknown Thrive Automator
fixed in 11.2