CVE-2026-11435
SQL Injection in Jinher OA
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 |
|---|---|---|
| jinher_network | jinher_oa | 1.0 |
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
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing parameterized queries and strict input validation on the "httpOID" parameter to prevent SQL injection.
Additional measures involve applying the principle of least privilege to database accounts, conducting thorough code security audits, deploying web application firewalls, and performing regular security testing.
Can you explain this vulnerability to me?
CVE-2026-11435 is a critical SQL injection vulnerability found in Jinher OA version 1.0, specifically in the nextselectplan.aspx file. The issue arises because the httpOID parameter is directly concatenated into SQL queries without proper validation or parameterization.
This flaw allows unauthenticated attackers to execute arbitrary SQL commands on the backend Microsoft SQL Server database remotely by manipulating the httpOID argument.
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to sensitive data stored in the backend database.
Attackers may escalate privileges, potentially execute remote code, and completely compromise the Jinher OA system.
Since no authentication is required to exploit this vulnerability, it poses a significant security risk.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by sending specially crafted HTTP GET requests to the vulnerable "nextselectplan.aspx" page, targeting the "httpOID" parameter with SQL injection payloads.
Detection methods include using time-based delays or checking for database-specific responses such as database name retrieval to confirm SQL injection.
- Example command using curl to test for SQL injection with a time delay payload: curl "http://target/nextselectplan.aspx?httpOID=1;WAITFOR DELAY '00:00:05'--"
- Example command to check database name: curl "http://target/nextselectplan.aspx?httpOID=1;SELECT DB_NAME()--"
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The SQL injection vulnerability in Jinher OA 1.0 allows unauthorized access to sensitive data and potential full system compromise. Such unauthorized data access and potential data breaches can lead to non-compliance with common standards and regulations like GDPR and HIPAA, which require protection of personal and sensitive information.
Failure to properly secure the application against this vulnerability could result in exposure of personal data, violating data protection requirements and potentially leading to legal and financial penalties under these regulations.