/

CVE-2026-19905

Severity:

HIGH RISK

(7.3)

SQL Injection (CWE-89) in Jinher OA Attendance Approval

CVE-2026-19905

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-74, CWE-89

Impact:

Unauthorized Database Access and Data Manipulation

Severity:

HIGH RISK

(7.3)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A high-severity SQL injection vulnerability in Jinher OA 1.0 affects the attendance approval endpoint when processing the httpOID argument. Because the endpoint is remotely reachable, an attacker may be able to manipulate database queries and access, alter, or disrupt application data.

Affected context

The vulnerability occurs in the Jinher OA 1.0 attendance approval functionality at /C6/JHSoft.Web.HrmAttendance/attendance_out_approve.aspx. It becomes risky when the remotely supplied httpOID value is incorporated into database operations without sufficient parameterization, validation, or contextual escaping.

Exploit preconditions

  • Attack surface: Remotely accessible web application endpoint
  • Required access: Access to send requests to the attendance approval functionality; authentication requirements may depend on deployment configuration
  • Trigger point: Processing of the httpOID argument
  • Why exploitation is possible: Attacker-controlled input may influence SQL query construction rather than being handled exclusively as data

Why this happens

The underlying issue is improper neutralization of externally controlled input used in a database query. When application code builds SQL statements by concatenating or interpolating untrusted values, specially crafted input can alter the intended query structure. This maps primarily to CWE-89: Improper Neutralization of Special Elements used in an SQL Command (SQL Injection); the related CWE-74 classification reflects broader injection into an interpreter or command-processing context.

Potential impact

  • An attacker may read sensitive records from the application database
  • Unauthorized users could modify or delete business data
  • Database integrity and application availability could be disrupted
  • Exposed credentials or sensitive records could support further compromise
  • Auditability and trust in attendance records could be reduced

General mitigation guidance

Mitigation generally focuses on ensuring that external input cannot change SQL command structure.

Common defensive patterns include:

  • Using parameterized queries or well-designed query-builder abstractions
  • Applying strict allowlist validation for identifier-like values such as httpOID
  • Avoiding dynamic SQL construction from request parameters
  • Restricting database accounts to the minimum required privileges
  • Separating database credentials and limiting access to sensitive tables
  • Returning generic database errors without exposing query details
  • Enforcing authentication and authorization checks at the endpoint and record level

How teams detect issues like this

Organizations can look for SQL injection risks through:

  • Static analysis rules identifying string concatenation or interpolation in SQL construction
  • Code review checks for request parameters passed directly to database APIs
  • Dynamic testing that uses non-destructive injection probes in authorized environments
  • Web application firewall or gateway policies detecting anomalous database-oriented input
  • Database logs showing unusual query structure, error patterns, or access to unexpected tables
  • Automated security review tools that flag unsafe query-building patterns

Sources

SourceLink
github.comgithub.com/pangdudu24/cve/issues/1
vuldb.comvuldb.com/cve/CVE-2026-19905
vuldb.comvuldb.com/submit/870787
vuldb.comvuldb.com/vuln/390110
vuldb.comvuldb.com/vuln/390110/cti

Frequently asked

questions

Yes. The affected attendance approval function is exposed through a web endpoint, so an attacker who can reach it may submit maliciously constructed input. The exact scope depends on network exposure and access controls.

The description does not establish whether authentication is required. The practical prerequisite is the ability to reach the endpoint and have the request processed; deployment-specific authorization controls may limit access.

Use parameterized database queries or safe query abstractions, validate inputs according to their expected format, and avoid constructing SQL commands through string concatenation.

Combine secure database APIs with least-privilege database accounts, focused code review, automated static analysis, authorized security testing, and monitoring for anomalous query activity.

Find out what's already
exploitable in your codebase.