CVE-2026-4935

OttoKit: All-in-One Automation Platform < 1.1.23 - Unauthenticated SQL Injection

2026-05-11 00:00
Drew Webber (mcdruid)

Strategic Overview

Status
Patched in 1.1.23
Affected Plugin
OttoKit: All-in-One Automation Platform
Affected Version
< 1.1.23
CVSS
7.5High
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2026-4935
View all OttoKit: All-in-One Automation Platform vulnerabilities

At a glance

CVE-2026-4935 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the OttoKit WordPress plugin, affecting versions < 1.1.23. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 1.1.23; sites on affected versions should update now. Disclosed May 2026, reported by Drew Webber (mcdruid).

Vulnerability Overview

The OttoKit: All-in-One Automation Platform plugin for WordPress is vulnerable to SQL Injection in versions up to 1.1.23 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality.

CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Reaching this weakness in OttoKit < 1.1.23 takes no account at all. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.

A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For OttoKit the fix is 1.1.23: builds < 1.1.23 are affected, anything from 1.1.23 onward is not.

Remediation

Update to version 1.1.23, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: OttoKit 1.1.23 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-4935https://www.wordfence.com/threat-intel/vulnerabilities/id/5797e529-5109-49bf-a687-e5bf8f350c8fhttps://nvd.nist.gov/vuln/detail/CVE-2026-4935

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C