Loading vulnerability…
Easy Chat Server 3.1 contains a directory traversal vulnerability reachable via the UserName parameter. According to the provided content, a remote attacker can supply crafted path traversal sequences through this parameter to access files outside the intended directory scope. The available description further states that exploitation may lead not only to disclosure of sensitive information but also to arbitrary code execution. Specific vulnerable code paths, request handlers, or file-processing functions are not provided in the available material.
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.
This repository is a small standalone Python proof-of-concept for CVE-2026-36227 affecting Easy Chat Server 3.1. The repository contains one executable code file (poc.py) and several Markdown documents (README.md, PUBLIC-POC.md, ATTACK-SCENARIO.md) that describe the vulnerability, usage, impact, and mitigation. The exploit is not part of a larger framework. The core exploit logic is in poc.py. It constructs a raw HTTP POST request to the Easy Chat Server registration endpoint /registresult.htm and submits a crafted UserName parameter containing traversal sequences. The default payload is ../../ecs-traversal-proof.txt. The script manually URL-encodes form fields, preserves forward slashes in the username value, builds HTTP headers, and sends the request over a TCP socket to a user-supplied host and port. It also supports a --dry-run mode that prints the exact HTTP request without transmitting it, a configurable --username traversal value, and a socket timeout option. Exploit capability: the PoC demonstrates remote unauthenticated path traversal leading to unauthorized file write during user registration. It does not include a webshell, command execution payload, or post-exploitation logic. Instead, it is a benign verifier intended to confirm whether traversal components in UserName are preserved and acted upon by the server. If the vulnerable application writes into a web-executable or otherwise sensitive path, the underlying bug could potentially be escalated to remote code execution, but that escalation is not implemented here. Operationally, the script prints basic target information, sends the crafted request, and displays the first 500 bytes of the HTTP response. Success verification is manual: the operator is instructed to inspect the Easy Chat Server installation or web/root directory for the proof artifact. Overall, this is a genuine but limited POC exploit focused on demonstrating the vulnerable write primitive rather than weaponizing it.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.