Understand vulnerabilities. Protect your applications.
Discover which vulnerabilities affect your technologies and how to fix them. Explore clear explanations, affected versions and practical recommendations - from CMS platforms and plugins to application libraries.
Vulnerability archive 600
Reset filtersOpenClaw: Slack allowFrom could bind to mutable display names
OpenClaw: Skill Workshop apply flow could override pending approval
OpenClaw: QQBot streaming command could mutate config without explicit allowFrom
OpenClaw: Node pairing reconnection could confuse approval scope state
OpenClaw's Slack plugin approvals used the exec approver gate for plugin actions
OpenClaw: memory-wiki ingest could read local files with operator.write scope
OpenClaw: Scoped chat.send route inheritance could bypass admin command scope gates
OpenClaw's POSIX node system.run safe-bin allowlist could be widened by shell expansion
OpenClaw: QQBot native approval buttons did not enforce configured approver identity
OpenClaw: Hook-triggered CLI runs could receive owner MCP tool authority
OpenClaw: Control UI locality spoofing could mint a durable admin device token
OpenClaw: Same-host trusted-proxy deployments could accept local forged identity headers
OpenClaw's marketplace runtime extension metadata could point at unscanned payloads
OpenClaw's browser act interactions could bypass private-network navigation checks
OpenClaw: Shell wrapper argv could change between approval and execution
OpenClaw: Bundle MCP loopback could miss its exec denylist on session spawn
OpenClaw: Exec approval display truncation could hide the command being approved
OpenClaw: Message read actions could skip channel allowlist checks
OpenClaw MCP SSE redirects could forward Authorization headers
OpenClaw: Internal/webchat command auth could inherit ownerAllowFrom wildcard state
OpenClaw: Empty-scope device re-pairing could confuse caller scope containment
OpenClaw: Workspace-derived service PATH could influence trash command selection
OpenClaw: Workspace .env STATE_DIRECTORY could influence bundled runtime dependency roots
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.