Is this vulnerability remotely exploitable beyond the Slack workspace?

Exploitation occurs through Slack, but from OpenClaw's perspective it is effectively remote: any user with access to the Slack workspace where the integration is installed and `dmPolicy` is open can attempt to send privileged commands via direct message.

What level of access does an attacker need to exploit this?

An attacker generally needs to be a member of the Slack workspace and able to send direct messages to the OpenClaw app or bot. They do not need to be part of the intended allowlist or privileged access groups because the vulnerable DM handler does not enforce those checks.

What is the safest general fix pattern?

The safest fix is to centralize and standardize authorization so that every slash command—regardless of channel or DM context—verifies the caller's identity against a consistent, server-side permissions model. The DM handler should perform the same allowlist and access-group checks as other handlers, and `dmPolicy` should not bypass or weaken these checks.

Severity:

CRITICAL RISK

(9.8)

Incorrect Authorization (CWE-863) in OpenClaw Slack Slash-Command DM Handler

CVE-2026-28392

Published:

Mar 5, 2026

Status:

Received

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-78

CRITICAL RISK

CRITICAL

(9.9)

Command Injection in MCP Stdio Configuration Validation (CWE-78) in WeKnora

Remote Code Execution

March 7, 2026

CWE-89

CRITICAL RISK

CRITICAL

(9.9)

SQL Injection via PostgreSQL Array/Row Expressions (CWE-89) in WeKnora Query Engine

Remote Code Execution via SQL Injection on the Database Server

March 7, 2026

Vulnerability Type

Category:

Authorization Bypass

CWE:

CWE-863

Impact:

Privilege Escalation and Access Control Bypass

Severity:

CRITICAL RISK

(9.8)

CVSS Version:

3.1

Vulnerability Type

Category:

Authorization Bypass

CWE:

CWE-863

Impact:

Privilege Escalation and Access Control Bypass

Severity:

CRITICAL RISK

(9.8)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

START 14 DAYS FREE TRIAL

BOOK A DEMO

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Incorrect Authorization (CWE-863) in OpenClaw Slack Slash-Command DM Handler

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

CRITICAL RISK

CRITICAL

(9.9)

Command Injection in MCP Stdio Configuration Validation (CWE-78) in WeKnora

CRITICAL RISK

CRITICAL

(9.9)

SQL Injection via PostgreSQL Array/Row Expressions (CWE-89) in WeKnora Query Engine

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare