On this page (7 sections)
A critical flaw has been published for VITEC EZ TV Platform Server. According to the GitHub Advisory Database entry, versions before 8.5.0 contain an unrestricted file upload bug in the upload handler. An unauthenticated attacker on the network can place an ASPX file in a web-accessible uploads directory and have the web server run it.
If you operate, host or manage an EZ TV Platform Server, especially one reachable from the internet, treat this as a patch-now item. The research does not say whether the flaw is being exploited, so the safe assumption is that it can be.
What happened
The CVE record was published on November 13, 2026 and describes the issue in VITEC EZ TV Platform Server. The upload handler accepts a file from a remote client and takes the target filename from an X-FILENAME request header. Per the description, it requires no authentication and performs no file type validation.
The file lands in a web-accessible uploads directory, and the description says an uploaded ASPX file is immediately executable by the web server. The result is remote code execution in the context of the web server process. A VulnCheck advisory is listed as a reference, and its URL names an uploadhandler.ashx endpoint. The NVD entry repeats the same text as the GitHub advisory, so this is one description, not two independent confirmations.
Why this class of bug is so dangerous
Two weaknesses combine here. CWE-306 means a sensitive function is reachable without authentication. CWE-434 means the server accepts a dangerous file type without checking it. Alone, each is serious. Together they give an anonymous visitor a direct path from a single HTTP request to running code.
The CVSS v4 metrics in the advisory match that picture: network attack vector, low attack complexity, no attack requirements, no privileges, no user interaction, and high impact on confidentiality, integrity and availability of the vulnerable system. Nobody has to click anything, and no account is needed.
ASPX files are server-side pages. When a web server such as IIS treats an uploaded file in a served directory as executable, anything written there can become code running with the web server's permissions. That is why upload directories should never be both writable by the application and executable by the web server.
Who is affected
- Any deployment of VITEC EZ TV Platform Server older than 8.5.0 that has not received one of the listed patches (8.3.0, 8.3.1, 8.4.0, 8.4.1).
- Servers whose web interface or upload handler can be reached from the internet, a guest network or a broad internal network.
- Hosting providers and integrators who run EZ TV Platform on behalf of customers and may not track its version.
The description says patches are available for 8.3.0, 8.3.1, 8.4.0 and 8.4.1, and that users on releases prior to 8.3.0 should upgrade to 8.5.0 or later. The wording does not explain how these patched builds relate to the 8.5.0 line, which is another reason to confirm with the vendor.
How to check your exposure
- Find every EZ TV Platform Server instance you run, including test, staging and customer-hosted ones, and record the installed version from the product's own admin or about screen.
- Compare each version with the patch guidance above. Anything before 8.3.0 needs a move to 8.5.0 or later; the 8.3 and 8.4 lines need the patched builds named in the advisory.
- Check whether the web interface is reachable from outside your trusted network, from a machine that is not on your internal network.
- Look in the uploads directory on the server for files you did not put there, particularly .aspx files, and review file creation times against your normal activity.
On a Windows server, this PowerShell command lists ASPX files under a directory and their modification times. It is read-only. Replace the path with the actual uploads directory of your installation, which the research does not specify, and look for unfamiliar files or recent timestamps.
Get-ChildItem -Path "C:\path\to\uploads" -Recurse -Filter *.aspx | Sort-Object LastWriteTime -Descending | Select-Object FullName, CreationTime, LastWriteTime, LengthAlso review web server access logs for requests to the upload handler that carry an unusual X-FILENAME header, or for requests to uploaded .aspx files shortly after an upload. IIS does not log custom request headers by default, so a missing header in the logs does not prove nothing happened.
What to do now
- Inventory all EZ TV Platform Server instances and note their versions.
- Contact VITEC or use its official download channel to get the patched build for your release line, and confirm the exact fixed version.
- Upgrade releases before 8.3.0 to 8.5.0 or later; apply the 8.3.0, 8.3.1, 8.4.0 or 8.4.1 patches if you are on those lines.
- Until patched, restrict network access to the server so only trusted addresses can reach its web interface, using a firewall or reverse proxy rule.
- Search the uploads directory for unexpected .aspx files and review web server logs for unusual upload requests.
- If you find a suspicious file, isolate the server, preserve logs and the file for investigation, and rotate any credentials or secrets the server could read.
- After patching, confirm the version and re-check the uploads directory for leftovers from before the update.
Detection and monitoring afterwards
Because exploitation can leave a web shell or similar file in a served directory, file integrity matters. Alert on new executable file types appearing in upload locations, and on web server processes starting unexpected child processes. Keep the server's access logs long enough to look back at the period before you patched.
For an internet-facing instance, a website firewall rule that blocks uploads of script file types is a useful extra layer, though it is no substitute for the vendor patch. You can also run a Webforta scan on a site you have verified to review what is exposed from the outside, and monitoring can flag changes to certificates, DNS and headers. Neither replaces checking the server itself.
What is still unknown
- Whether attackers are exploiting CVE-2026-82504. The sources do not say, and the CVE data shows no CISA KEV entry.
- The exact patched build numbers and how they map to each release line, since the GitHub entry lists them as Unknown.
- The default location of the uploads directory, which the research does not give.
- Whether a public proof of concept exists. The research does not state it.
Only one independent publisher, VulnCheck, is named as a reference beyond the CVE record itself, so details may be refined as VITEC or others publish more. Check the vendor's own notices for updates.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
