2.3

CVSS Score

4.0

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

CVE-2026-27484

CVE-2026-27484: OpenClaw Discord moderation authorization used untrusted sender identity in tool-driven flows

Overview

Discord moderation action handling (timeout, kick, ban) used sender identity from request parameters in tool-driven flows, instead of trusted runtime sender context.

Impact

In setups where Discord moderation actions are enabled and the bot has the necessary guild permissions, a non-admin user could request moderation actions by spoofing sender identity fields.

Affected Packages / Versions

Package: openclaw (npm)
Latest published affected version (as of 2026-02-19): 2026.2.17
Affected range: <=2026.2.17
Fixed in planned next release: 2026.2.18

Fix

Moderation authorization now uses trusted sender context (requesterSenderId) instead of untrusted action params.
Added permission checks for required guild capabilities per action.

Fix Commit(s)

775816035ecc6bb243843f8000c9a58ff609e32d

Thanks @aether-ai-agent for reporting.

(GitHub Advisory)

Miggo Vulnerability Database

→

CVE-2026-27484

CVE-2026-27484:

2.3

CVSS Score

4.0

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
openclaw	npm	< 2026.2.18	2026.2.18

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability exists because the application used an untrusted sender identity from request parameters for authorization in Discord moderation actions (timeout, kick, ban). This allowed a non-admin user to potentially execute these actions by spoofing the sender's identity. The fix was to introduce and consistently use a trusted requesterSenderId from the server-side context for all moderation-related authorization checks.

The analysis of the patch commit 775816035ecc6bb243843f8000c9a58ff609e32d reveals the key functions involved. The function handleDiscordModerationAction in src/agents/tools/discord-actions-moderation.ts is the primary vulnerable function, as it directly executed the moderation commands without proper authorization checks. The patch adds a call to the new verifySenderModerationPermission function to fix this.

The function tryHandleDiscordMessageActionGuildAdmin in src/channels/plugins/actions/discord/handle-action.guild-admin.ts was also vulnerable because it was responsible for calling the moderation action handler but failed to provide the trusted sender's ID, thereby enabling the vulnerability. The patch corrects this by extracting the requesterSenderId from the context and passing it to the action handler.

Finally, handleDiscordMessageAction in src/channels/plugins/actions/discord/handle-action.ts was changed to accept the requesterSenderId in its context, enabling the trusted identity to be passed down through the call chain. The absence of this in the function's context was a contributing factor to the vulnerability.

Vulnerable functions

handleDiscordModerationAction

src/agents/tools/discord-actions-moderation.ts

This function was responsible for handling Discord moderation actions like 'timeout', 'kick', and 'ban'. Before the patch, it executed these actions without verifying if the user requesting the action had the necessary permissions. The patch added the `verifySenderModerationPermission` call, which checks the sender's permissions before executing the action. An attacker could have exploited this by sending a request with spoofed parameters to perform moderation actions they were not authorized to do.

tryHandleDiscordMessageActionGuildAdmin

src/channels/plugins/actions/discord/handle-action.guild-admin.ts

This function acts as a wrapper that prepares and calls the main moderation action handler (`handleDiscordAction`). The vulnerability here is that it did not extract the sender's identity from a trusted source (`ctx.requesterSenderId`) and pass it to the action handler for authorization. Instead, the downstream handler relied on untrusted parameters from the request. The patch ensures that the trusted `requesterSenderId` is used, preventing unauthorized users from performing moderation actions.

handleDiscordMessageAction

src/channels/plugins/actions/discord/handle-action.ts

This function is an entry point for handling various Discord message actions. The vulnerability lies in the fact that its context (`ctx`) did not include the `requesterSenderId`, a trusted source for the sender's identity. This meant that any downstream moderation actions called from this function would not have the necessary information to perform proper authorization checks. The patch modifies the function signature to include `requesterSenderId` and `toolContext` in `ctx`, allowing it to pass the trusted sender's identity for authorization.

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.