CVE-2025-10090
BaseFortify
Publication date: 2025-09-08
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 |
|---|---|---|
| jinher | jinher_oa | to 1.2 (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-2025-10090 is a critical SQL injection vulnerability in Jinher OA up to version 1.2, specifically in the /C6/Jhsoft.Web.departments/GetTreeDate.aspx component. The vulnerability occurs because the 'id' parameter is improperly handled and directly concatenated into SQL queries without proper validation or parameterization. This allows unauthenticated remote attackers to inject arbitrary SQL commands into the backend database, potentially compromising data confidentiality, integrity, and availability. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive user and business data, potential privilege escalation through database access, possible remote code execution on the database server, and complete compromise of the Jinher OA system and its data. Since it can be exploited remotely without authentication, attackers can manipulate the database to disrupt operations or steal confidential information. [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 endpoint /C6/Jhsoft.Web.departments/GetTreeDate.aspx for SQL injection on the 'id' parameter. One method is to send HTTP GET requests with SQL injection payloads such as `id=1;WAITFOR+DELAY+'0:0:5'--` to observe if there is a time delay indicating SQL injection. Additionally, Google dorking can be used to identify vulnerable targets by searching for `inurl:C6/Jhsoft.Web.departments/GetTreeDate.aspx`. Example command using curl to test the delay payload: `curl "http://target/C6/Jhsoft.Web.departments/GetTreeDate.aspx?id=1;WAITFOR+DELAY+'0:0:5'--"` and observe response time. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing parameterized queries with prepared statements to prevent SQL injection, enforcing strict input validation and filtering on all user inputs, applying the principle of least privilege to database accounts, conducting comprehensive code security audits, and deploying a web application firewall (WAF) as a temporary protective measure. Regular security and penetration testing should also be performed to identify and address vulnerabilities. [2]