CVE-2026-2952 is a high severity flaw (CVSS 7.3) in Vaelsys 4.1.0. A POST request handler in the tree server script passes the xajaxargs argument into a system call, which allows OS command injection. It can be attempted remotely, and the exploit is public.
What's affected
The NVD record lists Vaelsys version 4.1.0. The NVD record does not name a fixed version, so assume every copy you run is exposed until the maintainer says otherwise. The vendor was contacted early about this disclosure but did not respond, according to the record. The public disclosure and the record are the only sources for this issue.
How to check if you're exposed
Find out whether Vaelsys 4.1.0 runs anywhere in your environment, including test servers and old demos. Search the web root for tree/tree_server.php, which the record names, and review access logs for requests to it.
Then check who can reach it. A copy that is open to the internet is the case that matters most, so review the web server, reverse proxy and firewall rules for that host.
What to do now
- Remove Vaelsys 4.1.0 from any internet-facing host, or restrict it to a trusted network or VPN.
- Check the project page and the maintainer's contact channels for a fix, and apply it if one has appeared since this was written.
- Block
/tree/tree_server.phpat the proxy if you can, or require authentication in front of it. - Run the service under a low privilege account and isolate the host.
- Check the host for unexpected processes, scheduled tasks and accounts, and rebuild it if anything looks wrong.
- Keep a list of small third party applications like this one, so a new advisory can be matched against it quickly. The Gold page for this CVE has the latest data: https://gold.safeguard.sh/vulnerability/CVE-2026-2952
Why it matters
The record files this under CWE-77 and CWE-78. The input reaches a system command without being neutralised. CWE-78 covers OS command injection, where a value that should be plain data ends up inside a command line that the server runs. The server process then runs commands chosen by the attacker, with whatever rights the web service has. The usual fix is to avoid the shell, or to validate input against a strict allowlist, and that is a change for the maintainer.
The NVD description says the exploit is public, so anyone can read how the weakness works. A public write-up and no vendor fix is a poor mix for a system that holds real data, which is why exposure control is the main defence here. The record does not mark this CVE as exploited in the wild, and it is not in the CISA KEV catalog.
Quick check
Did the vendor respond?
According to the record, no.
Does this need a login?
The CVSS vector lists no privileges required.
Sources
Last reviewed: 19 October 2026.
