Skip to main content
Menu
CVEs

Brainstorm Force OttoKit unauthenticated SSRF in plugin's request handling

Affects the OttoKit WordPress plugin by Brainstorm Force, versions 1.1.42 and earlier. Fixed in 1.1.43.

CVE-2026-129029Published , updated

7.2HighCNA
Exploited
No known exploitation
Fix
Fixed in 1.1.43
Who is exposed
Not reported

Summary

Brainstorm Force's OttoKit plugin for WordPress, the affected software, contains a Server-Side Request Forgery flaw. An attacker can reach it remotely, without logging in, and use it to make the server send requests to destinations of the attacker's choosing.

Written by a model

Original description

Server-Side Request Forgery (SSRF) vulnerability in Brainstorm Force OttoKit suretriggers allows Server Side Request Forgery.This issue affects OttoKit: from n/a through 1.1.42.

Who should check

Teams running the OttoKit WordPress plugin (Brainstorm Force, suretriggers) at version 1.1.42 or earlier, such as WordPress site operators and hosts

“WordPress OttoKit Plugin <= 1.1.42 is vulnerable”

patchstack.com

What to do

Upgrade to a fixed version: 1.1.43.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-129029 (WordPress OttoKit plugin <= 1.1.42 - Server Side Request Forgery (SSRF) vulnerability), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129029 (entry last updated 2026-11-20):
Affected:
- Brainstorm Force OttoKit: fixed in 1.1.43
Fixed versions: 1.1.43.
Conditions (all must be true for the bug to be hit):
- Brainstorm Force OttoKit WordPress plugin version 1.1.42 or earlier (source: https://patchstack.com/database/wordpress/plugin/suretriggers/vulnerability/wordpress-ottokit-plugin-1-1-42-server-side-request-forgery-ssrf-vulnerability?_s_id=cve)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-129029 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129029 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://patchstack.com/database/wordpress/plugin/suretriggers/vulnerability/wordpress-ottokit-plugin-1-1-42-server-side-request-forgery-ssrf-vulnerability?_s_id=cve
- https://www.cve.org/CVERecord?id=CVE-2026-129029
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129029
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129029"}.

Affected versions

cve.now Index

27Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.2/10CVSS 7.2
  • No patch0/5No signal

What would change the score

  • Would score about 72 if added to CISA KEV
  • Would score about 67 if CISA's SSVC rates exploitation active
  • Would score about 32 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Evidence 3

Questions about CVE-2026-129029

Is CVE-2026-129029 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

The bug is a server-side request forgery, which lets an attacker make the WordPress server connect to internal systems. This can leak data from behind the firewall.

Source: patchstack.com, cve.org

Which versions are affected by CVE-2026-129029?

suretriggers: through 1.1.42 (fixed in 1.1.43).

Source: cve.now feed data

Am I affected, and how do I check?

OttoKit plugin versions 1.1.42 and earlier, from Brainstorm Force, are affected. To check an installed copy, look at the plugin version shown on the WordPress Plugins screen.

Source: patchstack.com, cve.org

How do I fix CVE-2026-129029?

Update the OttoKit plugin to the latest available version, which must be at least 1.1.43, as the vendor advises.

Source: patchstack.com, cve.org

No corrections so far. Something wrong on this page? Report an error.