/

CVE-2026-19344

Severity:

HIGH RISK

(7.3)

SQL Injection (CWE-89) in Code-Projects Task System

CVE-2026-19344

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-74, CWE-89

Impact:

Database compromise and unauthorized data access

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

Code-Projects Task Management System 1.0 contains a SQL injection vulnerability in the user comment-count functionality. If the remotely supplied task_id value is incorporated into a database query without adequate parameterization, an attacker may influence query behavior and potentially access or modify application data.

Affected context

The vulnerability occurs in the /user/comment_count_user.php endpoint when it processes the task_id argument. Risk depends on whether the endpoint is reachable by an attacker and whether the supplied value is used in database operations without consistent input validation and parameterized query handling.

Exploit preconditions

  • Attack surface: The remotely accessible /user/comment_count_user.php endpoint
  • Required access: Network access to the application; authentication requirements depend on deployment configuration
  • Trigger point: Processing of the task_id request argument
  • Why exploitation is possible: The argument may influence a database query without sufficient separation between data and SQL syntax

Why this happens

The underlying bug is an injection flaw caused by treating externally supplied input as part of a database command. When request parameters are concatenated into SQL statements or otherwise reach query construction without parameterized handling, an attacker may alter the intended query logic. This maps primarily to CWE-89: Improper Neutralization of Special Elements used in an SQL Command (SQL Injection); CWE-74 broadly describes the related injection class.

Potential impact

  • An attacker may read unauthorized records
  • An attacker could alter or delete application data
  • Database credentials or sensitive metadata may be exposed
  • Application integrity and task or comment records may be compromised
  • Depending on database privileges, the vulnerability may enable broader backend impact

General mitigation guidance

Mitigation generally focuses on ensuring that all database operations treat request values strictly as data.

Common defensive patterns include:

  • Use parameterized queries or prepared statements for every database operation
  • Apply allowlisted type and range validation to identifiers such as task_id
  • Avoid constructing SQL statements through string concatenation
  • Run the application with a database account limited to required operations and tables
  • Centralize database access patterns so unsafe query construction is less likely to recur
  • Return generic errors without exposing query details or database internals

How teams detect issues like this

Organizations can identify similar issues through:

  • Static analysis rules that flag string concatenation or interpolation in SQL construction
  • Code review checks for direct use of request parameters in database APIs
  • Dynamic testing of identifier parameters with unexpected type, boundary, and metacharacter inputs
  • Web application firewall or database monitoring policies for anomalous query patterns
  • Automated security review tools that identify missing parameterization and weak input validation

Sources

SourceLink
code-projects.orgcode-projects.org/
github.comgithub.com/littleRain1355/PHPissue/issues/3
vuldb.comvuldb.com/cve/CVE-2026-19344
vuldb.comvuldb.com/submit/865361
vuldb.comvuldb.com/vuln/387180
vuldb.comvuldb.com/vuln/387180/cti

Frequently asked

questions

It may be remotely exploitable when the affected endpoint is reachable over the network and the task_id value reaches a vulnerable database query. Authentication and authorization controls may limit the practical scope.

The attacker needs network access to the endpoint. Whether an authenticated session is required depends on how the application exposes and protects the user functionality.

Use parameterized queries or prepared statements, validate task_id according to its expected type and range, and ensure database errors are not exposed to users.

Standardize safe database-access libraries, enforce least-privilege database accounts, review all request-to-query data flows, and include SQL injection testing in development and deployment checks.

Find out what's already
exploitable in your codebase.