Loading vulnerability…
CVE-2026-67595 is a supply-chain style compromise affecting VaahCMS versions 2.0.0 through 2.3.4. A malicious obfuscated JavaScript payload was embedded in the Blade template used to render security OTP emails. When the affected template is rendered in a JavaScript-capable browser context, the injected script executes unauthorized code in the victim's browser. The payload establishes a WebSocket connection to a hardcoded command-and-control service, uses MutationObserver to detect and hook dynamically added password fields for keystroke capture, scrapes WhatsApp Web DOM content, and accepts remote commands that can redirect the page or overwrite rendered content. The issue is consistent with inclusion of hidden malicious functionality in distributed application code.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.