Disclosed weakness · no CVE recorded
Obot sibling-domain requests could perform actions as a signed-in user
Obot · Obot Platform · MCP gateway
First documented disclosure · Review checkpoint
Summary
An attacker-controlled sibling origin could make a signed-in browser perform authorized POST actions in Obot.
Severity and exploitation evidence
High · 7.1/10 · CVSS 3.1. Severity source.
Exploitation not established: The reviewed sources establish the weakness or a controlled demonstration; malicious exploitation against users is not established.
Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.
How the weakness works
State-changing cookie-authenticated requests lacked an origin check; text/plain bodies were accepted as JSON.
Conditions required
The attacker can serve script from another origin on the same site, and a signed-in user or browser holding an unexpired bootstrap cookie opens it.
Potential impact
Actions use the victim’s role; Owner/Admin actions can include attacker-controlled accounts, MCP servers or model endpoints. Responses cannot be read by this attack.
Affected versions and configurations
<= 0.28.1.
Fix and mitigation status
0.28.2 fixes this issue.
Practical next steps
Upgrade to 0.28.2; avoid placing untrusted applications under the same site and review unauthorized POST actions.
Operating lesson
Check request origin as well as authentication before accepting browser state changes.
Evidence and limits
The complete advisory was published November 20, after the November 19 release. The maintainer assigns the CVSS score. No CVE is assigned in the reviewed advisory. Tagged production code contains the named correction. Only POST is exploitable under the reported CORS policy. Bearer/API-key authentication is outside this cookie-based issue. A parent domain with no untrusted script origins is outside the described exposure.
Sources
- Obot advisory GHSA-jwgp-hqmv-m4p6
Primary source ·
- Obot 0.28.2 release notes
Primary source ·
- Obot 0.28.2 issue-specific correction
Primary source ·