On this page (7 sections)
A critical vulnerability, CVE-2026-14914, has been published for Tegsoft Contact Center. It is an unrestricted file upload flaw that, according to the GitHub Advisory Database entry, allows an attacker to upload a web shell to the web server. The listed scope is Tegsoft Contact Center builds before latest-202611161510.
If you run Tegsoft Contact Center, especially with its web interface reachable from the internet, treat this as an urgent patching and exposure-review task. Public detail is thin so far, so this article separates what is confirmed from what is not.
What has been published
The advisory describes an unrestricted upload of a file with a dangerous type in Tegsoft Contact Center, a product from Tegsoft Yönetim ve Bilişim Hizmetleri Tic. Ltd. Şti. The impact it names is uploading a web shell to a web server. The record was published on November 20, 2026, and it is also reflected in the NVD entry, which repeats the same description rather than adding independent confirmation.
The advisory also points to a Turkish national cyber security bulletin, TR-26-1588. The research available for this article does not include its contents, so check it directly for any vendor guidance.
Why this weakness class is serious
CWE-434 covers software that accepts uploaded files without properly restricting their type, so that dangerous files end up where the server can process them. A web shell is a small script that, once it sits on a web-accessible path and is executed by the server, gives an attacker a remote control panel on that machine.
The CVSS vector in the advisory explains the 10.0 score. It is reachable over the network, low complexity, needs no privileges and no user interaction, and the scope is changed, with high impact on confidentiality, integrity and availability. In plain terms, the scoring assumes an unauthenticated remote attacker could take over the system and affect resources beyond the vulnerable component. The research does not give the exact upload mechanism, so do not assume which endpoint or feature is involved.
For a contact center platform, a takeover can matter beyond the server itself. Such systems commonly sit close to call records, customer data, telephony integrations and internal networks. That is general context rather than a finding from the advisory, but it is why a compromise here deserves a wide investigation.
Who is exposed
- Organizations running Tegsoft Contact Center on a build older than latest-202611161510.
- Installations whose web interface is reachable from the internet or from large, loosely controlled internal networks.
- Hosting providers and integrators who operate Tegsoft instances on behalf of customers.
- Teams that cannot say which build they run. Unknown version should be treated as potentially affected until verified.
How to check your exposure
Start with the version. The exact way to read the build string depends on how Tegsoft was installed and the vendor's tooling, which the research does not cover. Check the product's admin or about page, your deployment records, or ask the vendor or your integrator, then compare the result with latest-202611161510.
Next, look for signs that something has already been uploaded. The commands below are generic read-only checks and assume you know the web root of your installation, which the research does not specify. Replace /path/to/webroot with it. This lists files modified in the last 14 days with common server-side script extensions, so unexpected entries stand out:
find /path/to/webroot -type f -mtime -14 \( -name '*.php' -o -name '*.jsp' -o -name '*.jspx' -o -name '*.war' -o -name '*.sh' \) -lsThen search the web server access logs for upload-style POST requests followed by requests to newly created files. Adjust the log path to your setup. Look for POST requests from unfamiliar addresses and for scripts being requested that you do not recognize:
grep -F '"POST ' /var/log/your-web-server/access.log | tail -n 200A clean result does not prove the system is clean, since logs can be incomplete or tampered with. It only means these simple checks found nothing.
What to do now
- Identify every Tegsoft Contact Center instance you run and record its build version.
- Contact Tegsoft or your integrator to confirm the fixed build and get the update. Move to latest-202611161510 or later, since the affected range is builds before it.
- Read the national advisory TR-26-1588 for any vendor guidance or workarounds.
- Until patched, restrict access to the web interface to trusted networks or a VPN, and remove direct internet exposure where you can.
- Take a backup or snapshot before patching, so you can investigate later if you find signs of compromise.
- Run the file and log checks above on every instance, including those you have just patched, because patching does not remove a shell that was already uploaded.
- If you find a suspicious file or unexplained access, isolate the host, preserve logs, rotate credentials and secrets used by or stored on the system, and follow your incident process.
Detection and monitoring afterwards
Keep watching the server after the patch. Alert on new or changed script files in web-accessible directories, unexpected outbound connections from the Tegsoft host, new administrative accounts, and unusual spikes of POST requests. File integrity monitoring on the web root is a cheap way to catch an uploaded shell early.
From the outside, you can review what your public endpoints expose with a read-only security scan and keep an eye on certificate and header changes with monitoring. These show your external surface, not what is inside the application, so they do not replace patching. If you suspect a compromise, the guide on what to do when a website is hacked lays out the response steps.
What we do not know yet
- The exact upload feature or path that is vulnerable.
- Whether the fix is distributed as the build latest-202611161510 itself or a later one. The sources only say the issue affects builds before it.
- Whether anyone is exploiting it. The research reports no exploitation and no CISA KEV listing as of November 20, 2026.
- Who reported the flaw and who assigned the score. The GitHub page says the record was published by the National Vulnerability Database.
We will treat this as developing. Check the vendor and the national advisory for updates, and re-evaluate if exploitation reports appear.
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.
