Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-wh94-p5m6-mr7j | OpenClaw Discord moderation authorization used untrusted sender identity in tool-driven flows |
Wed, 25 Feb 2026 09:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Mon, 23 Feb 2026 20:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:node.js:*:* | |
| Metrics |
cvssV3_1
|
Mon, 23 Feb 2026 15:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Openclaw
Openclaw openclaw |
|
| Vendors & Products |
Openclaw
Openclaw openclaw |
Sat, 21 Feb 2026 09:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | OpenClaw is a personal AI assistant. In versions 2026.2.17 and below, the Discord moderation action handling (timeout, kick, ban) uses sender identity from request parameters in tool-driven flows, instead of trusted runtime sender context. In setups where Discord moderation actions are enabled and the bot has the necessary guild permissions, a non-admin user can request moderation actions by spoofing sender identity fields. This issue has been fixed in version 2026.2.18. | |
| Title | OpenClaw Discord moderation authorization used untrusted sender identity in tool-driven flows | |
| Weaknesses | CWE-862 | |
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-02-24T18:14:56.099Z
Reserved: 2026-02-19T19:46:03.541Z
Link: CVE-2026-27484
Updated: 2026-02-24T18:14:48.074Z
Status : Analyzed
Published: 2026-02-21T10:16:12.557
Modified: 2026-02-23T20:44:09.190
Link: CVE-2026-27484
No data.
OpenCVE Enrichment
Updated: 2026-04-17T17:00:10Z
Github GHSA