Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach exposed web application over network
-
ExploitIdentify unsanitized input parameter
-
ExecutionInject crafted SQL via HTTP request
-
ImpactExfiltrate database contents
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The affected software must be deployed and network-reachable (the single reference is a Turkish national CERT bulletin, suggesting primarily Turkish deployments). Per the CVSS vector (AV:N/AC:L/PR:N/UI:N), no authentication and no user interaction are required, so exposed instances up to and including the 2026-10-16 build are reachable by remote unauthenticated attackers against default configurations. The available sources do not identify the specific vulnerable endpoint, parameter, protocol, or configuration setting that triggers the SQL injection - the exact trigger is not described in the available sources. The principal limiting factor is deployment scarcity: the product has a very small installed base, and only internet- or network-exposed instances are at practical risk. |
| Impact | This is a network-exploitable SQL injection (CWE-89) with a vendor/NVD CVSS 3.1 vector of AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N (7.5, High). The scoring signals easy, remote, unauthenticated exploitation (PR:N) with high confidentiality impact but no integrity or availability impact - consistent with data exfiltration rather than data tampering or service disruption. The vuln.today decision label is 'this_week', indicating elevated but not emergency priority. No EPSS score, no CISA KEV listing, and no public PoC or exploit reference are present in the input, so there is no evidence of active exploitation or published exploit code at time of analysis. The practical risk ceiling is therefore lower than the raw 7.5 suggests for most organizations because the affected software - an inventory tracking application from a single, apparently Turkish vendor (Starnet Computer and Network Systems) - has a very limited real-world footprint. The main limiting factor on risk is prevalence, not exploitability: where the product IS deployed and internet-exposed, an unauthenticated attacker could read database contents, but the population of exposed instances is likely small. Note: the affected-version field is expressed only as a date range ('through 2026-10-16') with no discrete fixed version, and no vendor advisory URL beyond the TR national CERT bulletin is provided, so exact patch status could not be independently confirmed. |
| Exploit ScenarioDerived | An unauthenticated remote attacker identifies a web-facing input (e.g., a search, login, or query parameter) in the Inventory Tracking Application that is not properly sanitized and injects crafted SQL to read back database contents such as credentials or inventory/business records. Because the CVSS vector is AV:N/AC:L/PR:N/UI:N, this requires only network reachability and a single crafted request, with no authentication or user interaction. No public exploit code or PoC reference is identified in the available sources, so any exploitation would currently require an attacker to develop their own payload. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 02, 2026
Unauthenticated SQL injection in Starnet Computer and Network Systems' Inventory Tracking Application (all builds through 2026-10-16) lets remote attackers reach the backend database and read data they should never see, rated CVSS 3.1 7.5 with confidentiality-only impact (C:H/I:N/A:N). Per the vector AV:N/AC:L/PR:N/UI:N, no credentials and no user interaction are required, so any internet- or network-exposed deployment on a default configuration is directly reachable. No public exploit code was identified at time of analysis and the CVE is not in CISA KEV; practical risk is dominated by deployment scarcity, since the product has a very small installed base and only exposed instances are realistically at risk (vuln.today priority: this_week).
RemediationAI
No vendor-released patch or fixed version is identified in the available data; the affected range is stated as 'through 2026-10-16', so a build dated after that may address the flaw, but that is not confirmed by any advisory and must be verified with Starnet Computer and Network Systems before relying on it. Until a confirmed fix exists, treat every deployed instance as vulnerable and act on exposure first: remove the application from direct internet reachability by placing it behind a VPN or a reverse proxy with IP allow-listing (effective against remote unauthenticated attacks per AV:N/PR:N, but it blocks legitimate off-network users and does not stop attackers already inside the trusted network). Second, front the application with WAF rules targeting SQL-injection payloads in query strings and form bodies (fast to deploy and reversible, but signature-based filtering is bypassable and produces false positives on legitimate data entry, so it is a stopgap only). Third, reduce blast radius by running the application's database account at least privilege, removing DDL and write rights where the feature set allows and restricting it to the minimum schemas required (this caps the confidentiality loss the injection can cause, at the cost of possibly breaking inventory write or report functions that must then be re-granted selectively). Finally, enable and review database and web-server query logging for anomalous SQL syntax in request parameters to detect attempted exploitation, and consult bulletin TR-26-1441 at https://siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-26-1441 for any updated vendor guidance.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is CWE-89, improper neutralization of special elements used in an SQL command, i.e. classic SQL injection where attacker-controlled input is concatenated into a database query instead of being bound through parameterized statements or a validated allow-list. The affected technology is a web-facing inventory/asset tracking web application published by Starnet Computer and Network Systems; the CPE cpe:2.3:a:starnet_computer_and_network_systems:inventory_tracking_application:*:*:*:*:*:*:*:* carries an unconstrained version wildcard, so the vendor simply states the defect affects the product through the 2026-10-16 build rather than naming a discrete release range. Because the injection yields high confidentiality impact with no integrity or availability impact in the assessed vector, the realistic outcome is arbitrary read of database contents (inventory records, user tables, credentials or tokens stored in the schema) rather than data destruction or command execution. Notably, the available sources do not identify the specific vulnerable endpoint, parameter, HTTP method, or configuration setting that carries the injectable input - the trigger is not described in the available sources. The only reference is Turkish national CERT bulletin TR-26-1441 (siberguvenlik.gov.tr), which suggests the disclosure and the observed deployments are primarily Turkish; that is a sourcing signal, not a technical constraint on exploitation.
Know when Inventory Tracking Application gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Unauthenticated remote SQL injection (PR:N, AV:N, AC:L) with database read exposure gives C:H; the sources show no integrity or availability impact, so I:N/A:N.
Primary rating from Vendor (TR-CERT).
CVSS VectorVendor: TR-CERT
DescriptionCVE.org
Improper neutralization of special elements used in an SQL command ('SQL injection') vulnerability in Starnet Computer and Network Systems Inventory Tracking Application allows SQL Injection.
This issue affects Inventory Tracking Application: through 2026-10-16.
Executive ViewAI
Starnet's Inventory Tracking Application contains a high-severity SQL injection flaw (CVE-2026-74993) that allows remote, unauthenticated attackers to directly read backend databases. While the product has a very small installed base, any organization running an internet-exposed instance could suffer unauthorized data disclosure. Leadership should care because a breach could expose sensitive inventory and operational data, though the limited deployment footprint reduces the likelihood of widespread impact.
No vendor-released patch identified at time of analysis. Interim mitigations include network segmentation, restricting access via firewall rules or VPN, and enabling database activity monitoring to detect anomalous queries.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
EUVD-2026-115183
GHSA-8f2x-6wpj-gj49
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB