Termix (a web-based server management platform) versions 1.7.0 through 1.9.0 contain a stored cross-site scripting vulnerability in the File Manager component. The FileViewer implementation (src/ui/desktop/apps/file-manager/components/FileViewer.tsx) renders SVG file content without sanitization. An attacker able to place a crafted SVG file into a managed server’s filesystem can cause arbitrary JavaScript to execute in the Termix application context when a Termix user previews the file via the File Manager.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
Repository contains a single Python PoC exploit (exploit.py) plus README and .gitignore. The PoC targets Termix (Electron app) stored XSS in the File Manager’s SVG rendering (unsafe dangerouslySetInnerHTML per README; advisory GHSA-m3cv-5hgp-hv35). Exploit flow: (1) authenticate to Termix backend at http://localhost:30001 (login, else register) and set Authorization: Bearer <token>; (2) enumerate and then create a managed SSH host entry pointing to 127.0.0.1:22 with username 'kali' and key-based auth, generating an RSA keypair at /home/kali/CVE-2026-22804/poc_key and appending the public key to ~/.ssh/authorized_keys; (3) initiate an SSH session via the file-manager service at http://localhost:30004 and poll /ssh/status; (4) upload cookie_stealer.svg to /home/kali via /ssh/uploadFile. The uploaded SVG embeds HTML/JS via <foreignObject> and triggers execution using an <img onerror> handler; when a user views the SVG in Termix’s File Manager, it reads localStorage and document.cookie and displays them (overlay + alert), demonstrating session hijacking within the Electron context. No external C2/exfil endpoint is used; data is shown locally in the UI.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
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.