CVE-2025-56385: A SQL injection vulnerability exists in the login functionality of WellSky Harmony version 4.1.0.2.83 withi...
A SQL injection vulnerability exists in the login functionality of WellSky Harmony version 4.1.0.2.83 within the 'xmHarmony.asp' endpoint. User-supplied input to the 'TXTUSERID' parameter is not properly sanitized before being incorporated into a SQL query. Successful authentication may lead to authentication bypass, data leakage, or full system compromise of backend database contents.
Security readout for executives and security teams
Plain-English summary
CVE-2025-56385 is a critical SQL injection issue reported in WellSky Harmony 4.1.0.2.83 login handling. If exploitable, an unauthenticated attacker could bypass authentication, expose sensitive data, or compromise backend database contents. The public record does not identify a fixed version.
Executive priority
Treat as urgent for any confirmed WellSky Harmony 4.1.0.2.83 deployment. The risk is critical because the reported flaw affects login and could expose regulated or operationally sensitive database contents without prior authentication.
Technical view
The issue is CWE-89 in xmHarmony.asp, where TXTUSERID is reportedly incorporated into a SQL query without proper sanitization. CVSS 3.1 is 9.8: network-reachable, low complexity, no privileges, no user interaction, with high confidentiality, integrity, and availability impact.
Likely exposure
Likely exposure is limited to organizations running WellSky Harmony version 4.1.0.2.83, especially where the login endpoint is externally reachable. The source bundle’s structured affected-product fields are incomplete, so asset owners should confirm versions directly with WellSky records or support.
Exploitation context
The source bundle says this CVE is not in KEV, and no cited source confirms active exploitation. Public details identify the endpoint and parameter, increasing discovery risk, but exploitation status is not established from the provided evidence.
Researcher notes
Evidence supports critical SQL injection risk, but product metadata is incomplete: vendor, product, CPE, and fixed-version fields are not populated in the supplied structured record. Do not assume other WellSky products or versions are affected without vendor confirmation.
Mitigation direction
Check WellSky guidance or support for fixed versions and official remediation.
Restrict access to the Harmony login endpoint to trusted networks where feasible.
Review web application firewall rules for SQL injection detection and blocking.
Preserve relevant web, application, and database logs for investigation.
Assess whether exposed systems require credential rotation or database review.
Validation and detection
Inventory WellSky Harmony deployments and confirm whether version 4.1.0.2.83 is present.
Identify whether xmHarmony.asp is reachable from the internet or untrusted networks.
Review logs for abnormal TXTUSERID input and unusual login outcomes.
Confirm whether vendor advisories name a patched build or supported workaround.
Document compensating controls if immediate remediation is unavailable.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.