Which versions of OpenClaw Dashboard are affected by CVE-2026-66418?

OpenClaw Dashboard v3.0.0 contains a critical stored XSS vulnerability affecting audit logging, with no public exploit identified at time of analysis.

How to fix or mitigate CVE-2026-66418?

Within 24 hours: Restrict audit log access to a minimal set of trusted administrators and monitor failed login attempts for suspicious username patterns. Within 7 days: Deploy WAF rules to sanitize or block XSS payloads in username fields and configure real-time alerting on audit log access events. Within 30 days: Request patch timeline from OpenClaw; upon patch release, prioritize testing and immediate deployment across all affected instances; if no patch emerges, initiate procurement and migration to an alternative dashboard solution.

OpenClaw Dashboard CVE-2026-66418

Q: What is the CVSS score of CVE-2026-66418?

CVE-2026-66418 has a CVSS 4.0 base score of 9.3 (Critical). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.3%.

EUVD-2026-51309 CRITICAL

Cross-site Scripting (XSS) (CWE-79)

2026-07-30 VulnCheck

GHSA-jgjm-xq9g-p8xp

XSS Openclaw Dashboard Tugcantopaloglu

9.3

CVSS 4.0 · Vendor: VulnCheck

Severity by source

Vendor (VulnCheck) PRIMARY

9.3 CRITICAL

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

9.3 CRITICAL

Unauthenticated network injection (PR:N/AV:N/AC:L) requiring admin panel view (UI:R); execution in admin context crosses a trust boundary (S:C) yielding high C/I, no availability impact.

3.1 AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Scope

Lifecycle Timeline

Analysis Generated

Jul 30, 2026 - 21:32 vuln.today

CVE Published

Jul 30, 2026 - 20:55 cve.org

CRITICAL 9.3

DescriptionCVE.org

OpenClaw Dashboard v3.0.0 contains a stored cross-site scripting vulnerability that allows unauthenticated remote attackers to inject arbitrary HTML and script payloads by submitting a crafted username in a failed login POST request, which is recorded verbatim in the audit log. When an administrator opens the notification panel, the unescaped log entry is rendered via innerHTML with a permissive Content-Security-Policy allowing inline event handlers, enabling the attacker-supplied payload to execute in the administrator's session and interact with authenticated endpoints including agent instruction file editing and configuration changes.

AnalysisAI

Stored cross-site scripting in OpenClaw Dashboard v3.0.0 lets an unauthenticated remote attacker seed a malicious payload simply by submitting a crafted username in a failed login attempt, which the audit log stores verbatim. When an administrator later opens the notification panel, the log entry is rendered through innerHTML under a permissive CSP that permits inline event handlers, executing the payload in the admin's authenticated session and enabling full account takeover. No public exploit was identified at time of analysis, though a dedicated write-up advisory exists; the CVSS 4.0 base score is 9.3 (Critical), reflecting the account-takeover impact.

Technical ContextAI

The affected component is OpenClaw Dashboard (CPE cpe:2.3:a:tugcantopaloglu:openclaw-dashboard), a web-based management dashboard for the OpenClaw agent platform. The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation). Two compounding design flaws are present: user-controlled input (the login username) is persisted to the audit log without output encoding, and that log is later injected into the DOM via the JavaScript innerHTML sink rather than a safe text-assignment API such as textContent. A defense-in-depth control that should mitigate DOM injection - Content-Security-Policy - is configured permissively enough to allow inline event handlers (e.g. onerror/onload), so the payload executes even without inline <script> blocks. Because the sink executes in the administrator's already-authenticated browser context, the XSS pivots directly into privileged application actions (agent instruction-file editing and configuration changes).

RemediationAI

No vendor-released patch or fixed version was identified in the provided data, so track the upstream project at https://github.com/tugcantopaloglu/openclaw-dashboard for a corrected release and consult the advisories at VulnCheck (https://www.vulncheck.com/advisories/openclaw-dashboard-stored-xss-via-failed-login-username-field) and theopaid's write-up. Until a patch exists, apply specific compensating controls: change the notification-panel rendering to inject log entries via textContent or an HTML-escaping/sanitization step (e.g. DOMPurify) instead of innerHTML, which eliminates script execution but is a code-level change requiring a rebuild; tighten the Content-Security-Policy to remove 'unsafe-inline' and disallow inline event handlers, which blocks the payload but may break legitimate inline handlers elsewhere in the UI and needs regression testing; and validate/encode the username field at the audit-logging boundary so payloads are neutralized before storage. As an operational stopgap, restrict network access to the dashboard's login and admin interfaces to trusted management networks and consider a WAF rule to strip HTML/script metacharacters from the login username parameter, accepting that WAF filtering of a free-form field is best-effort and bypassable.