CVE-2026-14914: Critical Tegsoft File Upload Flaw
Critical CVSS (10.0) reachable over local.
TL;DR - CVE-2026-14914 is a CVSS 10.0 unrestricted file-upload vulnerability that can permit web-shell placement on a Tegsoft Contact Center server. - Tegsoft Contact Center versions before
latest-202611161510are affected; upgrade to that release marker or a newer vendor release. - No confirmed exploitation or public PoC was identified, and the CVE is not listed in CISA KEV. Internet-facing systems still require urgent review.
Summary
CVE-2026-14914 affects Tegsoft Contact Center, a platform developed by Tegsoft Yönetim ve Bilişim Hizmetleri Tic. Ltd. Şti. The Tegsoft Contact Center vulnerability is described as an unrestricted upload of a file with a dangerous type. The vulnerable functionality may allow an attacker to upload a web shell to the web server.
A web shell can provide server-side command execution when the uploaded file is stored in a web-accessible location and interpreted by the application or web server. The practical impact depends on the service account’s privileges, network access, operating-system controls, and whether the upload directory permits script execution.
Even without confirmed exploitation, internet-facing or untrusted-network deployments warrant immediate review. Organizations unfamiliar with web-shell risks can also review this WebAuthn glossary guide for broader application-security context.
| Field | Value |
|---|---|
| CVE ID | CVE-2026-14914 |
| Product | Tegsoft Contact Center |
| Vendor | Tegsoft Yönetim ve Bilişim Hizmetleri Tic. Ltd. Şti. |
| Vulnerability | Unrestricted upload of file with dangerous type |
| CVSS score | 10.0 Critical |
| Attack vector | Not provided in the available CVE record |
| Authentication required | Not provided in the available CVE record |
| Patch status | Yes; fixed/latest marker identified as latest-202611161510 |
| Affected versions | Tegsoft Contact Center versions before latest-202611161510 |
| CISA KEV | Not listed as of 2026-11-20 |
The available record does not include a complete CVSS vector. The attack vector and authentication requirements should not be inferred from the 10.0 score alone. Defenders should validate those details against the vendor advisory or a subsequent authoritative update.
Root Cause
The reported root cause is insufficient restriction and validation of uploaded files. The application appears to permit a file type that can be interpreted as executable server-side code instead of limiting uploads to safe content and ensuring that upload destinations cannot execute scripts.
An unrestricted upload flaw is more serious than the ability to store arbitrary documents. If an attacker can control the filename, extension, contents, or destination path, they may be able to place a web shell under a web-accessible directory. A subsequent request to that file can cause the web server or application runtime to execute attacker-controlled code.
The available NVD description does not identify the affected endpoint, upload parameter, required request format, authentication boundary, or server runtime. Those details matter for precise detection and validation, but they should not delay containment.
Review every upload function exposed by the affected deployment, particularly endpoints that accept server-side templates, scripts, archives, images, or contact-center attachments.
The record does not provide a CWE classification. It explicitly characterizes the issue as “Unrestricted upload of file with dangerous type” and states that the impact can include uploading a web shell to the web server. That description supports treating the vulnerability as a potential path to arbitrary server-side code execution.
Who’s Exposed
The affected product is Tegsoft Contact Center. The available affected-version expression is:
All versions before
latest-202611161510
This is a vendor build or release marker rather than a conventional semantic version such as 5.4.2. The available CVE data does not provide a more granular numeric version range. Administrators should compare the deployed build identifier with latest-202611161510 and obtain vendor confirmation if their inventory uses a different naming scheme.
Deployments are especially exposed when the contact-center application:
- Is internet-facing
- Has a public login or upload interface
- Uses a web server capable of executing uploaded scripts
- Runs with broad filesystem or network permissions
- Stores uploads beneath a web-accessible directory
Internal-only deployments are not automatically safe. Compromised employee endpoints, remote-access accounts, third-party integrations, or adjacent applications may provide access to the vulnerable functionality.
Potentially affected environments include production contact-center servers, application servers behind reverse proxies, staging systems copied from production, and high-availability nodes that may not be patched uniformly. Load balancers and clustered deployments can conceal an outdated node. Verify the build on every backend rather than checking only the public frontend.
No affected operating-system distribution or separate client component is identified in the available information. Assess the issue at the Tegsoft Contact Center server and application-deployment level.
Severity Breakdown
NVD assigns CVE-2026-14914 a CVSS base score of 10.0, Critical. That rating reflects the potentially severe outcome of uploading a web shell to a server. Successful exploitation could allow server-side code execution under the identity and privileges of the web application or web server process.
The complete CVSS vector was not included in the returned CVE data. Therefore, the following components cannot be stated authoritatively:
- Attack Vector: unknown from the available record
- Attack Complexity: unknown
- Privileges Required: unknown
- User Interaction: unknown
- Scope: unknown
- Confidentiality impact: unknown
- Integrity impact: unknown
- Availability impact: unknown
The requested authentication requirement is also unknown. Do not assume that authentication is required merely because the product is commonly deployed behind a login. Verify the vendor advisory, application configuration, and relevant access-control rules.
If an upload endpoint is unauthenticated or reachable through a low-privilege account, practical risk may be higher than in an authenticated-only deployment.
Use the 10.0 score for prioritization, not as a substitute for environment-specific analysis. A web shell can expose credentials, contact-center data, call recordings, configuration secrets, integrations, and internal network connectivity. The final impact depends on containment controls and the privileges of the affected service account.
Analyst’s Take: Upgrade exposed Tegsoft Contact Center instances first, then verify the build on every backend node. The CVSS score is critical, but the missing vector, endpoint details, and authentication requirements mean defenders should validate local exposure rather than infer those conditions from the score alone.
Exploitation Status
CVE-2026-14914 is not listed in the CISA Known Exploited Vulnerabilities catalog based on the lookup performed on 2026-11-20. There is no CISA catalog date, due date, required action, or ransomware campaign flag associated with the CVE in the available data.
No confirmed exploitation in the wild was identified in the retrieved authoritative sources. A verified public proof of concept was also not identified. The current status is:
- Confirmed exploitation: Not known from the available sources
- Public PoC: No verified public PoC identified
- CISA KEV: Not listed
These findings do not establish that exploitation is impossible or absent. The stated web-shell impact makes the vulnerability attractive to attackers, and exploitation may occur privately or remain undetected. Prioritize internet-facing systems even without a KEV listing or public exploit.
Security teams should distinguish between “no evidence found” and “evidence of no exploitation.” Review local telemetry, web access logs, endpoint detection data, file-integrity records, and outbound network activity before concluding that a system is clean.
Sources
The primary vulnerability record is the National Vulnerability Database entry for CVE-2026-14914:
The CVE record identifies a Turkish national cybersecurity advisory as a reference:
The advisory page is delivered through a JavaScript application, and the retrieved HTML did not expose the substantive technical text. The affected range and fixed release marker used in this article are therefore limited to the information available in the NVD record and associated research note.
For product context and vendor identification:
The available source data does not provide a complete CVSS vector, a precise endpoint, a conventional numeric version range, a verified public exploit, or confirmed exploitation evidence. Track those gaps during remediation, but do not delay upgrading exposed Tegsoft Contact Center deployments.
This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.
Detection Guidance
Detection should combine version validation, web-server telemetry, filesystem review, and endpoint monitoring. Identify every Tegsoft Contact Center instance and record its exact build marker. Any deployment below latest-202611161510 should be treated as vulnerable until upgraded or otherwise confirmed by Tegsoft.
Investigate upload events followed by requests for newly created files. Pay particular attention to files with script-like extensions, double extensions, executable content, suspicious random names, or locations beneath web roots and temporary upload directories.
A web shell may not use an obvious filename, so content and execution behavior are more reliable indicators than extension alone.
Technical Notes
A generic web-server query can help identify suspicious upload-to-execution sequences. Field names vary by platform, so adapt the query to your SIEM schema:
index=web
| eval uri_l=lower(uri_path), method_l=upper(http_method)
| where method_l IN ("POST","PUT")
| search uri_l="*upload*" OR uri_l="*file*"
| join type=inner session_id [
search index=web
| eval uri_l=lower(uri_path)
| where http_method="GET"
| search uri_l IN ("*.php","*.asp","*.aspx","*.jsp","*.jspx","*.cgi","*.pl")
]
| table _time src_ip user uri_path http_status bytes_out
If the web server uses a combined access-log format, start with patterns that identify upload requests and subsequent script requests:
POST /<upload-endpoint> ... 2xx
GET /<web-root-or-upload-path>/<unexpected-script> ... 200
The endpoint name is not provided in the CVE record, so <upload-endpoint> must be replaced with the actual Tegsoft route discovered from application logs or normal traffic. Do not treat this generic pattern as a confirmed exploit signature.
On Linux systems, administrators can inspect recently modified files beneath likely web roots and upload directories:
find /var/www /opt/tegsoft -type f -mtime -14 \\
\( -iname '*.php' -o -iname '*.asp' -o -iname '*.aspx' -o -iname '*.jsp' \\
-o -iname '*.jspx' -o -iname '*.cgi' \) -printf '%TY-%Tm-%Td %TH:%TM %u %p\\n'
Review process and network telemetry for the web service account as well. Unexpected shells, interpreters, archive tools, credential utilities, or outbound connections initiated by the application process should be escalated for incident response.
These checks are indicators, not proof of compromise. Preserve evidence before deleting suspicious files.
Remediation Steps
Upgrade every Tegsoft Contact Center instance to the vendor’s fixed/latest release identified as:
latest-202611161510
The available information does not provide a conventional numeric fixed version. Use the vendor’s distribution channel or support process to obtain the release, and verify that each node reports a build equal to or newer than this marker.
In clustered environments, check all application servers, standby nodes, staging systems, and disaster-recovery images.
Before upgrading:
- Capture configuration and relevant logs.
- Confirm backup integrity.
- Confirm rollback procedures.
- Identify every backend node and deployment.
- Restrict unnecessary public access to the application.
After upgrading, test legitimate upload workflows while verifying that executable server-side content cannot be stored in a web-executable directory. A reverse proxy or web application firewall does not replace the vendor fix.
Technical Notes
The exact installer and package name are not provided in the available advisory data, so no vendor-specific package command can be stated safely. The operational upgrade action is to obtain the Tegsoft release corresponding to latest-202611161510 and apply it through the vendor-supported update mechanism.
Verify the deployed build afterward using the product’s administrative interface, service metadata, or vendor-provided version command.
As an interim Linux web-server control, disable script execution in upload directories. For Apache, a location-specific configuration may resemble:
<Directory "/path/to/tegsoft/uploads">
Options -ExecCGI
AllowOverride None
Require all granted
</Directory>
For NGINX, ensure upload paths cannot be passed to a scripting backend. A generic example is:
location ^~ /uploads/ {
try_files $uri =404;
# Do not include a fastcgi_pass, uwsgi_pass, or proxy rule
# that sends uploaded files to an application interpreter.
}
These examples require validation against the actual Tegsoft architecture. Incorrect web-server changes can disrupt legitimate functionality or fail to protect an alternate upload path.
Additional compensating controls include:
- Restricting access to the contact-center administration interface
- Placing the service behind a trusted VPN where operationally feasible
- Enforcing least privilege for the application account
- Applying server-side file-type allowlisting
- Storing uploads outside web roots
- Blocking script execution in upload directories
- Monitoring for unexpected child processes and outbound connections
Validation should inspect file contents and storage behavior rather than relying only on filename extensions.
If compromise is suspected, isolate the host or affected application tier, preserve logs and disk evidence, remove public access, and investigate for web shells, new accounts, scheduled tasks, credential theft, and lateral movement.
Rotate application secrets, service credentials, API tokens, and administrator credentials after determining the scope of exposure. Review outbound connections because a web shell may be used as an initial foothold for broader intrusion.
For additional vulnerability-tracking context, see our coverage of CVE-2026-19868.