CVE-2026-1050
BaseFortify
Publication date: 2026-01-17
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| risesoft-y9 | digital-infrastructure | to 9.6.7 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-1050 is a SQL injection vulnerability in the risesoft-y9 Digital-Infrastructure software up to version 9.6.7. It affects the REST Authenticate Endpoint, where user input parameters such as tenantShortName and loginName are not properly sanitized before being concatenated into SQL queries. Specifically, in the method getTenantByLoginName(String loginName) in Y9PlatformUtil.java, the loginName parameter is directly inserted into a SQL query string without using prepared statements or input validation. This allows an attacker to inject malicious SQL code remotely, potentially extracting sensitive database information or gaining full control over the server. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing remote attackers to perform SQL injection attacks on the affected system without authentication. Exploiting this flaw can lead to unauthorized access to sensitive database information, compromise of data confidentiality, integrity, and availability, and potentially full control over the affected server. This can result in data breaches, service disruption, and further exploitation of the system. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the vulnerable REST endpoints `/server-platform/services/rest/auth/authenticate3`, `/server-platform/services/rest/auth/authenticate5`, and `/server-platform/services/rest/v1/auth/authenticate3` for SQL injection flaws. A practical method is to use sqlmap, an automated SQL injection tool, to send crafted POST requests with manipulated parameters to these endpoints. For example, you can create a request file with the POST data targeting these endpoints and run sqlmap with high risk and level settings, such as `sqlmap -r request.txt --level=5 --risk=3 --dbs` to detect and enumerate databases. This approach confirms the presence of the SQL injection vulnerability by exploiting the unsanitized `tenantShortName` and `loginName` parameters. [1]
What immediate steps should I take to mitigate this vulnerability?
Currently, no official mitigations or patches have been provided by the vendor. Immediate steps include restricting access to the vulnerable REST endpoints to trusted networks or users, implementing web application firewall (WAF) rules to detect and block SQL injection attempts targeting these endpoints, and monitoring logs for suspicious activity. Additionally, consider replacing the affected component with an alternative product if feasible. Applying input validation and using prepared statements in the code are recommended long-term fixes but require vendor action. [2]