Repository navigation
v0.17.0
Added
MCP021: a click handler that dispatches a privileged action with no event.isTrusted check.
Claude for Chrome's own click-spoofing flaw is the confirmed root cause: a content-script click handler reads data-task-id off the clicked element and dispatches the associated agentic task, but never checks event.isTrusted. Reported to Anthropic's bug bounty program 2026-05-21, confirmed still broken against the shipped v1.0.80 on 2026-07-07 by Manifold Security (corroborated by Bleeping Computer and The Hacker News), no CVE assigned, unfixed as of the most recent reporting found. Any other script with DOM access on the page — commonly another installed browser extension — can forge the click a privileged action relies on.
New mcpscan/rules/dom_trust.py: fires on a click/onclick handler that reads element data (.dataset.x/getAttribute(...)) and forwards it to a privileged sink (extension messaging, or an approve/grant/authorize-named call), with no isTrusted check anywhere in the handler. Scoped to JS/TS source files only.
10 new tests, 141 passing (was 131). Dogfood self-scan clean.
See CHANGELOG.md for full details.