HomeWordPress vulnerabilitiesOttoKit
OttoKit vulnerabilities
OttoKit has 3 known vulnerabilities in this database. The most recent published record is dated 8 May 2026.
- Known vulnerabilities
- 3
- Active installs
- 90,000+
- Latest version
- 1.1.40
- Last updated
- 24 Sep 2026
- Most recent
- 8 May 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| SQL injection CVE-2026-4935 | High 8.6 | Before 1.1.23 | Fixed in 1.1.23 | 8 May 2026 |
| Authentication bypass CVE-2025-3102 | High 8.1 | Up to 1.0.78 | Fixed in a later version (latest 1.1.40) | 10 Apr 2025 |
| Cross-site scripting (XSS) CVE-2024-5485 | Medium 6.4 | Up to 1.0.47 | Fixed in a later version (latest 1.1.40) | 4 Jun 2024 |
Read the published descriptions
- CVE-2026-4935, 8 May 2026
- The OttoKit: All-in-One Automation Platform WordPress plugin before 1.1.23 does not properly sanitize user input before using it in a SQL statement, which could allow unauthenticated attackers to perform SQL injection attacks. CVE record
- CVE-2025-3102, 10 Apr 2025
- The SureTriggers: All-in-One Automation Platform plugin for WordPress is vulnerable to an authentication bypass leading to administrative account creation due to a missing empty value check on the 'secret_key' value in the 'autheticate_user' function in all versions up to, and including, 1.0.78. This makes it possible for unauthenticated attackers to create administrator accounts on the target website when the plugin is installed and activated but not configured with an API key. CVE record
- CVE-2024-5485, 4 Jun 2024
- The SureTriggers - Connect All Your Plugins, Apps, Tools & Automate Everything! plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Trigger Link shortcode in all versions up to, and including, 1.0.47 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
What to do if you run OttoKit
If you run OttoKit, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new OttoKit vulnerabilities
Free. We email you when a new vulnerability is published for OttoKit, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.