CVE-2025-27007

OttoKit: All-in-One Automation Platform (Formerly SureTriggers) <= 1.0.82 - Unauthenticated Privilege Escalation

2025-04-30 00:00
Denver Jackson

Strategic Overview

Status
Patched in 1.0.83
Affected Plugin
OttoKit: All-in-One Automation Platform
Affected Version
<= 1.0.82
CVSS
9.8Critical
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-27007
View all OttoKit: All-in-One Automation Platform vulnerabilities

At a glance

CVE-2025-27007 is a critical-severity Missing Authorization vulnerability in the OttoKit WordPress plugin, affecting versions <= 1.0.82. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.0.83; sites on affected versions should update now. Disclosed April 2025, reported by Denver Jackson.

Vulnerability Overview

The OttoKit: All-in-One Automation Platform (Formerly SureTriggers) plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 1.0.82. This is due to the create_wp_connection() function missing a capability check and insufficiently verifying a user's authentication credentials. This makes it possible for unauthenticated attackers to establish a connection, which ultimately can make privilege escalation possible.

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, integrity, availability — full site compromise territory.

CWE-862: Missing Authorization

OttoKit <= 1.0.82 carries this weakness at create_wp_connection(), and reaching it takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For OttoKit the fix is 1.0.83: builds <= 1.0.82 are affected, anything from 1.0.83 onward is not.

Remediation

Update to version 1.0.83, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: OttoKit 1.0.83 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-27007https://www.wordfence.com/threat-intel/vulnerabilities/id/965dce53-2865-4179-9505-a64e4db1d1fdhttps://nvd.nist.gov/vuln/detail/CVE-2025-27007

Related records

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