Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privilege portal credentials
-
ExploitSubmit crafted SQL in request parameter
-
ExecutionBackend executes injected query
-
ImpactExtract confidential database records
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 | Exploitation requires a valid authenticated session on Vitals ESP with at least low-privilege access (CVSS PR:L) - it is not reachable by fully anonymous/unauthenticated attackers. No special non-default feature or configuration is named in the advisory; the injection appears reachable through normal authenticated application functionality against versions 0 through 6.1. Impact is bounded to reading database contents (VC:H, VI:N, VA:N), so it cannot by itself modify data or disrupt service. Limiting factors: the authentication requirement, confidentiality-only scope, and the product's narrow (predominantly Taiwanese enterprise) deployment base. |
| Impact | Signals are consistent and point to a moderate, not urgent, priority. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) describes a network-reachable, low-complexity SQL injection requiring low-privilege authentication (PR:L), with impact limited to confidentiality (VC:H, VI:N, VA:N) - i.e. database read/disclosure only, no integrity or availability loss. EPSS corroborates low near-term exploitation risk at 0.06% (17th percentile), and there is no CISA KEV listing and no public proof-of-concept referenced, so this is not an actively-exploited or widely-weaponized flaw. The requirement for valid authentication (PR:L) plus the confidentiality-only impact meaningfully lowers real-world risk below what the 7.1 base score might suggest. No conflicting signals were found: all sources agree the vector is network-based and authenticated. The main limiting factor is the niche, Taiwan-centric deployment footprint of Vitals ESP, which further constrains realistic attacker interest to targeted intrusions rather than mass exploitation. |
| Exploit ScenarioDerived | An attacker with a valid low-privilege account on a Vitals ESP enterprise portal submits crafted input to a vulnerable parameter, injecting SQL that the backend executes against the application database. This lets them read sensitive records (user data, HR/workflow content) beyond their authorization. No public exploit code is referenced, so exploitation would require the attacker to independently identify the injectable endpoint. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Oct 07, 2026
Authenticated SQL injection in Vitals ESP versions 0 through 6.1 (Galaxy Software Services) allows a remote attacker holding a valid low-privilege session to inject arbitrary SQL commands and read the contents of the underlying database. The flaw is rated CVSS 7.1 by the vendor-side vector (CVSS:4.0) and maps to an assessed high-confidentiality, no-integrity, no-availability impact (CVSS:3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N), so it cannot by itself alter data or take the service down - impact is bounded to information disclosure. No public exploit code has been identified at time of analysis, it is not listed in CISA KEV, and EPSS is very low at 0.06% (17th percentile), which combined with the authentication prerequisite and the product's predominantly Taiwanese enterprise deployment base keeps this a moderate-priority issue rather than an urgent one.
Earlier versions of this analysis (1)
RemediationAI
No vendor-released patch version is identified in the available intelligence, so the first step is to contact Galaxy Software Services or open a ticket referencing TWCERT-2025-14255 (https://www.twcert.org.tw/en/cp-139-10543-380bd-2.html) to obtain the fixed Vitals ESP build and confirm which release supersedes 6.1; plan the upgrade as soon as a patched build is published rather than waiting, since the entire 0-6.1 line is affected. Until then, prioritize compensating controls that match the actual attack path: (1) Restrict network exposure of the Vitals ESP web interface to trusted internal networks or a VPN, since the injection requires a valid session - this removes the remote attack surface entirely at the cost of losing external access for remote workers; (2) Enforce least privilege on application accounts and inventory/rotate any high-privilege database accounts the platform uses, so that successful injection reads the minimum possible data, accepting that this does not stop the injection itself; (3) Place the application behind a WAF with SQL-injection signatures and enable database query logging/alerting for anomalous UNION or boolean-pattern queries - a detective control with false-positive management overhead, not a fix; (4) Review the Vitals ESP database role configuration so that the application's DB user holds only the SELECT/DML rights it genuinely needs, reducing the confidentiality blast radius. Because authentication is required (PR:L per the assessed CVSS:3.1 vector), tightening account provisioning, enforcing strong authentication, and removing dormant accounts meaningfully reduce who can reach the vulnerable code path, but none of these substitutes for the vendor fix once it is available.
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 root cause class is CWE-89, Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection'), in the Vitals ESP enterprise knowledge-management platform from Galaxy Software Services. Untrusted input reaching a database query is not safely parameterized, so an attacker who can already reach application functionality with an authenticated session can append or alter SQL statements. Because the injection point is exercised through normal authenticated application features rather than a pre-auth or non-default component, the attack surface is bounded by the requirement for a valid session (PR:L in the assessed vector). The CPE string cpe:2.3:a:gss:vitalsesp:*:*:*:*:*:*:*:* and the EUVD version range "Vitals ESP 0 ≤ 6.1" indicate the entire 0.x-6.1 line is affected, with no patch version enumerated in the available intelligence. The confidentiality-only impact (VC:H with VI:N/VA:N) is consistent with read-oriented SQL injection against the application's backing database (e.g. UNION/error-based or blind boolean extraction of credential, configuration, or business records) rather than command execution or stored-procedure abuse.
Know when Vitalsesp 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
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Network-reachable injection by an authenticated low-privilege user with no interaction (PR:L, UI:N), causing database disclosure only, so C:H with I:N/A:N.
Primary rating from Vendor (cert).
CVSS VectorVendor: cert
Lifecycle Timeline
4DescriptionCVE.org
Vitals ESP developed by Galaxy Software Services has a SQL Injection vulnerability, allowing authenticated remote attackers to inject arbitrary SQL commands to read database contents.
Executive ViewAI
Organizations using Vitals ESP developed by Galaxy Software Services should be aware of notable risk from CVE-2025-14255, a SQL injection vulnerability rated CVSS 6.5. Exploitation could allow attackers to execute code or inject malicious input. Organizations should apply vendor updates when available and monitor for exploitation.
Apply vendor patch. If patching is delayed: deploy WAF rules, restrict network access, enable logging.
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.
Authenticated SQL injection in Galaxy Software Services' Vitals ESP (versions 0 through 6.3) lets a logged-in user pass
Arbitrary file read in Vitals ESP (Galaxy Software Services) versions 0 through 6.3 lets a remote attacker who already h
EUVD-2025-201695
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB