CVE-2026-67595: VaahCMS 2.0.0 - 2.3.4 Malicious JavaScript Supply Chain via security-otp.blade.php
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-11 15:49 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
VaahCMS versions 2.0.0 through 2.3.4 contain a malicious obfuscated JavaScript payload embedded in the Blade template responsible for rendering security OTP emails, allowing remote attackers to execute unauthorized code in any browser that renders the affected email template with JavaScript enabled. The payload establishes a WebSocket connection to a hardcoded command-and-control endpoint, installs a password-field keylogger using MutationObserver to capture dynamically added inputs, scrapes WhatsApp Web DOM content, and accepts remote commands to redirect or overwrite the rendered page.
Description quoted from the CVE record (assigned by VulnCheck, published 2026-07-29).
Weakness: Embedded Malicious Code
How it can be exploited
Exploitable over the network with low attack complexity only when specific conditions are present needing no privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: no. Technical impact: total.
Public exploit evidence (Exploit Observer)
Exploit Observer found 4 code repositories naming this CVE.
Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.
See all 7 references on Exploit Observer
Live scores
- EPSS
- 0.008
low predicted chance of attack - VEDAS
- 0.988
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- Suricata
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| webreinvent vaahcms | from 2.0.0 up to and including 2.3.4 | 8d7898f7a385 is not affected |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
Vendor guidance:
- Pull Request (issue-tracking, patch)
- Patch Commit (patch)
How to detect it
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-67595 VaahCMS Embedded Malicious JavaScript Supply-Chain Backdoor. Add them to your Suricata rule set and reload.
Show the rules
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-67595 VaahCMS Embedded Malicious JavaScript Supply-Chain Backdoor"; flow:established,to_client; file.data; content:"wss|3a|//tm.filter|3a|1512"; nocase; fast_pattern; content:"document.tmfilter"; nocase; classtype:web-application-attack; reference:cve,CVE-2026-67595; reference:url,https://www.exploit.observer/?keyword=CVE-2026-67595&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=vaahcms&match=exact; sid:1080602; rev:1;)
CVE-2026-67595.rules on GitHub
References
Vendor advisories and patches
- Pull Request (issue-tracking, patch)
- Patch Commit (patch)
Technical analysis and advisories
- https://www.vulncheck.com/advisories/vaahcms-malicious-javascript-supply-chain-via-security-otp-blade-php (third-party-advisory)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.
Supporting partners
