CVE-2026-11412
SQL Injection in Jinher OA C6
Publication date: 2026-06-06
Last updated on: 2026-06-06
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| beijing_jinhe_network | jinhe_oa | c6 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a SQL injection issue found in Jinhe OA C6, specifically in the 'queryID' parameter of the /C6/JHSoft.Web.ModuleCount/GetFormSn.aspx endpoint.
The application does not properly validate or filter user input for this parameter, allowing an attacker to inject malicious SQL commands directly into the database.
This can be exploited remotely without authentication, making it particularly dangerous.
A proof of concept shows that attackers can manipulate the 'queryID' parameter to execute SQL code, such as time-based delays to confirm database details.
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized access to the database and potential data breaches.
Attackers can execute arbitrary SQL commands, which may allow them to read, modify, or delete sensitive data.
Since the exploit does not require authentication, it increases the risk of remote attacks and compromise of the affected system.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'queryID' parameter in the /C6/JHSoft.Web.ModuleCount/GetFormSn.aspx endpoint for SQL injection flaws.
One common method is to use time-based SQL injection payloads to observe delays in the server response, which indicate successful injection.
- Use curl or similar tools to send requests with malicious payloads, for example: curl "http://target/C6/JHSoft.Web.ModuleCount/GetFormSn.aspx?queryID=1' WAITFOR DELAY '0:0:5'--"
- Use SQL injection detection tools like sqlmap targeting the vulnerable parameter: sqlmap -u "http://target/C6/JHSoft.Web.ModuleCount/GetFormSn.aspx?queryID=1" --batch
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the vulnerable endpoint and applying input validation and sanitization on the 'queryID' parameter.
If possible, implement web application firewall (WAF) rules to detect and block SQL injection attempts targeting this parameter.
Monitor logs for suspicious activity related to the /C6/JHSoft.Web.ModuleCount/GetFormSn.aspx endpoint and the 'queryID' parameter.
Since the vendor has not responded, consider isolating or limiting network exposure of the affected Jinhe OA C6 system until a patch or fix is available.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows for SQL injection via the 'queryID' parameter, which can lead to unauthorized access and potential data breaches.
Such unauthorized access and data breaches can negatively impact compliance with common standards and regulations like GDPR and HIPAA, which require protection of sensitive data and prevention of unauthorized data access.
However, the provided information does not explicitly detail the direct effects on compliance or specific regulatory impacts.