CVE-2026-11435
Deferred Deferred - Pending Action

SQL Injection in Jinher OA

Vulnerability report for CVE-2026-11435, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-06-06

Last updated on: 2026-06-08

Assigner: VulDB

Description

A security vulnerability has been detected in Jinher OA 1.0. This affects an unknown function of the file nextselectplan.aspx. Such manipulation of the argument httpOID leads to sql injection. The attack may be launched remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-06-06
Last Modified
2026-06-08
Generated
2026-07-17
AI Q&A
2026-06-06
EPSS Evaluated
2026-07-15
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
jinher_network jinher_oa 1.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
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 Quick Actions

Instant insights powered by AI
Executive Summary

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.

Detection Guidance

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()--"
Impact Analysis

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.

Compliance Impact

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.

Mitigation Strategies

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.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-11435. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart