cve.bz

CVE-2026-129029 WordPress OttoKit plugin <= 1.1.42 - Server Side Request Forgery (SSRF) vulnerability

7.2 highEPSS 0.4%Fix available

High (7.2) in brainstorm force ottokit. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.2 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
EPSS
0.4% estimated probability of exploitation activity in the next 30 days; 31st percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
Assigned by
Patchstack (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • Brainstorm Force OttoKit: fixed in 1.1.43

Ask an AI about this CVE

Show the promptExplain CVE-2026-129029 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-129029?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-129029?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-129029 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Brainstorm Force OttoKitthrough 1.1.42

Fixed in

ProductFixed in
Brainstorm Force OttoKit1.1.43

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

History

  1. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON