CVE-2026-32553

OttoKit: All-in-One Automation Platform <= 1.1.35 - Unauthenticated Server-Side Request Forgery

2026-08-14 00:00

Strategic Overview

Status: Patched in 1.1.36
Affected Plugin: OttoKit: All-in-One Automation Platform
Affected Version: <= 1.1.35
CVSS: 7.2High
Weakness type: CWE-918 · Server-Side Request Forgery (SSRF)
CVE: CVE-2026-32553

View all OttoKit: All-in-One Automation Platform vulnerabilities

At a glance

CVE-2026-32553 is a high-severity Server-Side Request Forgery (SSRF) vulnerability in the OttoKit WordPress plugin, affecting versions <= 1.1.35. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.1.36; sites on affected versions should update now. Disclosed August 2026, reported by Abduvoris Karimov.

Vulnerability Overview

The OttoKit: All-in-One Automation Platform plugin for WordPress is vulnerable to Server-Side Request Forgery in versions up to, and including, 1.1.35. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application which can be used to query and modify information from internal services.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-918: Server-Side Request Forgery (SSRF)

Reaching this weakness in OttoKit <= 1.1.35 takes no account at all. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.

The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. For OttoKit the fix is 1.1.36: builds <= 1.1.35 are affected, anything from 1.1.36 onward is not.

Remediation

Update to version 1.1.36, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: OttoKit 1.1.36 closes this, and updating the plugin is the step that ends it.

Firewall
Login Security
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-32553 https://www.wordfence.com/threat-intel/vulnerabilities/id/a284a028-90e8-4f6e-9ba1-a3a890705894 https://nvd.nist.gov/vuln/detail/CVE-2026-32553

Related records

Other vulnerabilities in OttoKit: All-in-One Automation Platform

CVSS Vector

7.2

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeChanged
ConfidentialityLow
IntegrityLow
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/