WordPress OttoKit plugin <= 1.1.35 - Server Side Request Forgery (SSRF) vulnerability

published 2026-08-18 2 mo ago modified 2026-10-22 17 d ago also EUVD-2026-60912

cvss: 7.2; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 18%
public exploits: 0; none known

Unauthenticated Server Side Request Forgery (SSRF) in OttoKit <= 1.1.35 versions.

Patch / fix

fixed in 1

Brainstorm Force OttoKit 1.1.36

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: partial
Assessed: 2 mo ago (2026-08-18)

Exploit prediction

0.27% chance of exploitation in the next 30 days, higher than 18% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	7.2	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Affected products

Brainstorm Force OttoKit

Classification

Weakness

CWE-918 Server-Side Request Forgery

Technology feeds

WordPress rss critical rss

References

patchstack.com /database/wordpress/plugin/suretriggers/vulnerability/wordpress-ottokit-plugin-1-1-35-server-side-request-forg
vdb-entry

Sources

CVE List CVE-2026-32553
NVD CVE-2026-32553

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.

Summary