OpenClaw CVE-2026-62206

Exploitation requires the attacker to hold at least low-level authenticated access to the OpenClaw instance (PR:L per CVSS 4.0). Critically, the AT:P metric and the description's explicit caveat confirm that a specific deployment condition must be present: the operator's configuration must allow lower-trust input to reach the Discord moderation action path. In deployments where moderation endpoints are accessible only to highly-privileged or internally-sourced callers, exploitation is blocked by the architecture rather than by authorization logic. Limiting factors include: the requirement for prior authentication, the operator-controlled routing that determines reachability, and the absence of confidentiality impact (VC:N), meaning data exfiltration is not a consequence. The attack does not require user interaction and operates over the network.

The CVSS 4.0 base score of 6.0 reflects a meaningful but operationally constrained risk. The network attack vector (AV:N) and no-user-interaction requirement (UI:N) indicate the attack can be initiated remotely without victim participation. Low privileges required (PR:L) narrows exposure to callers that already hold some level of authenticated access to the OpenClaw instance. The AT:P metric is the most significant moderating factor: exploitation is conditional on the operator's deployment routing lower-trust input to the affected path - not all configurations are vulnerable. No EPSS data was provided, and the vulnerability is absent from CISA KEV, suggesting no confirmed widespread or active exploitation at this time. The real-world priority is moderate: environments where untrusted or semi-trusted callers can interact with OpenClaw moderation paths should treat this as a genuine risk; tightly controlled deployments with restricted caller access face substantially lower exposure. EPSS score is unavailable, which limits probabilistic exploitation forecasting.

An attacker with low-level authenticated access to an OpenClaw-integrated Discord environment identifies that the moderation action endpoint does not enforce authorization checks for their privilege level. By sending a crafted moderation request - for example, a ban or kick command - directly to the vulnerable path, the attacker executes the action as if they held elevated moderator privileges, potentially removing legitimate users from a Discord server or disrupting community management workflows. No public exploit code has been identified, but the straightforward nature of the missing check lowers the bar for exploitation by any authenticated user who discovers the path.