CVE-2026-4935
SQL Injection in OttoKit WordPress Plugin
Publication date: 2026-05-08
Last updated on: 2026-05-08
Assigner: WPScan
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| suretriggers | suretriggers | to 1.1.23 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability exists in the OttoKit: All-in-One Automation Platform WordPress plugin (also referred to as SureTriggers) before version 1.1.23. It occurs because the plugin does not properly sanitize user input before using it in SQL statements. This improper sanitization allows unauthenticated attackers to perform SQL injection attacks by manipulating database queries.
Specifically, attackers can exploit a time-based blind SQL injection via the poll answer field, where the plugin directly inserts comma-separated answer IDs into an SQL IN() clause without parameterization. This enables attackers to execute arbitrary SQL commands on the database.
How can this vulnerability impact me? :
This vulnerability can have serious impacts as it allows unauthenticated attackers to execute arbitrary SQL commands on the affected WordPress plugin's database.
- Attackers could extract sensitive data such as administrator password hashes.
- It could lead to unauthorized access, data leakage, or manipulation of the website's database.
- Overall, it poses a high security risk with a CVSS score of 8.6.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing for SQL injection attempts targeting the poll answer field in the OttoKit: All-in-One Automation Platform WordPress plugin versions prior to 1.1.23. Specifically, time-based blind SQL injection techniques can be used to verify if the plugin improperly sanitizes user input.
A practical approach is to send crafted HTTP requests that inject SQL payloads into the poll answer field and observe the response time or behavior changes indicating successful injection.
- Use tools like curl or sqlmap to test the vulnerable endpoint by injecting SQL payloads in the poll answer parameter.
- Example curl command to test for time-based blind SQL injection (replace URL and parameter accordingly):
curl -X POST -d 'poll_answer=1 OR IF(SLEEP(5),1,0)' https://targetsite.com/wp-admin/admin-ajax.php?action=poll_vote
If the response is delayed by approximately 5 seconds, it indicates the presence of the SQL injection vulnerability.
What immediate steps should I take to mitigate this vulnerability?
The immediate and recommended mitigation step is to update the OttoKit: All-in-One Automation Platform WordPress plugin to version 1.1.23 or later, where the vulnerability has been fixed.
Until the update can be applied, consider disabling or restricting access to the vulnerable plugin functionality to prevent exploitation.
Additionally, monitor your logs for suspicious activity related to SQL injection attempts targeting the poll answer field.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows unauthenticated attackers to perform SQL injection attacks, potentially extracting sensitive data such as administrator password hashes. Such unauthorized access to sensitive data can lead to violations of data protection regulations like GDPR and HIPAA, which require safeguarding personal and sensitive information against unauthorized access and breaches.
Failure to properly sanitize user input and the resulting risk of data exposure can compromise compliance with these standards, as organizations must ensure the confidentiality and integrity of sensitive data.