OA - SQLi (CVE-2025-10090)
Description
A flaw has been found in Jinher OA up to 1.2. The impacted element is an unknown function of the file /C6/Jhsoft.Web.departments/GetTreeDate.aspx. Executing manipulation of the argument ID can lead to sql injection. The attack may be launched remotely. The exploit has been published and may be used.
psychologyCrowdSec Analysis
CVE-2025-10090 is a SQL injection vulnerability in Jinher OA up to version 1.2, specifically affecting the /C6/Jhsoft.Web.departments/GetTreeDate.aspx endpoint. By manipulating the ID parameter, remote attackers can exploit this flaw to execute unauthorized SQL commands, potentially leading to data leakage or modification. With a published exploit available, this vulnerability poses a significant risk for organizations using affected Jinher OA deployments.
CrowdSec has been tracking this vulnerability and its exploits since 30th of March 2026.
Data from the CrowdSec community indicates that exploitation of CVE-2025-10090 is highly selective and intelligence-driven. Threat actors use advanced reconnaissance and carefully choose their targets, often as part of sophisticated campaigns or advanced persistent threat operations. CrowdSec network telemetry also shows that exploitation of CVE-2025-10090 has significantly declined over the past week. Attack volumes are well below the long-term average, suggesting attackers are rapidly losing interest. The vulnerability appears to be falling out of active use across most threat landscapes.
Attackers exploit the /C6/Jhsoft.Web.departments/GetTreeDate.aspx endpoint by injecting SQL commands into the id parameter, often using time-based payloads such as WAITFOR DELAY to confirm the vulnerability.
Full Intelligence Available
Connect your API key to access CrowdSec scores, exploit timelines, and attacker IPs.
| Event | Date |
|---|---|
| CVE Published | 2025-09-08 |
| Rule Released | 2026-03-30 |
| CrowdSec First Seen | 2026-03-31 |
Related Weaknesses
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.
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.