/

CVE-2026-76762

Severity:

HIGH RISK

(7.3)

SQL Injection (CWE-89) in Assessment Management 1.0

CVE-2026-76762

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

A high-severity SQL injection vulnerability in code-projects Assessment Management 1.0 allows remotely supplied input in the userid parameter to influence database queries.

An attacker who can reach the affected /welcome.php functionality may be able to read, alter, or interfere with application data, depending on database permissions and query behavior.

Affected context

The vulnerability occurs in the Assessment Management 1.0 application, specifically in functionality associated with /welcome.php. It becomes risky when the remotely accessible userid input is incorporated into database operations without sufficient separation between user-controlled data and SQL commands.

Exploit preconditions

  • Attack surface: Remotely accessible web application endpoint
  • Required access: Ability to send requests to the affected /welcome.php functionality; authentication requirements may depend on deployment configuration
  • Trigger point: Processing of the userid argument
  • Why exploitation is possible: User-controlled input may influence SQL statements without adequate parameterization or contextual validation

Why this happens

The underlying bug is an injection flaw in which externally controlled input is treated as part of a database command rather than strictly as data. This maps primarily to CWE-89: Improper Neutralization of Special Elements used in an SQL Command (SQL Injection) and is also related to CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component. The insecure pattern generally occurs when application code constructs SQL queries through string concatenation or equivalent unsafe query composition.

Potential impact

  • An attacker may read sensitive database records
  • An attacker could modify or delete application data
  • The vulnerability may enable authentication or authorization bypass in affected workflows
  • Database credentials or other secrets could be exposed
  • Application availability may be affected through disruptive database operations

General mitigation guidance

Mitigation generally focuses on ensuring that database commands cannot be altered by input values.

Common defensive patterns include:

  • Use parameterized queries, prepared statements, or well-maintained data-access abstractions
  • Apply allowlist validation for identifiers and expected userid formats as an additional control
  • Avoid constructing SQL statements through string concatenation
  • Use database accounts with only the permissions required by the application
  • Keep sensitive data separated and restrict unnecessary database access from the web tier
  • Centralize query construction and establish secure-by-default data-access policies

How teams detect issues like this

Detection approaches commonly include:

  • Static analysis for SQL query construction involving request parameters
  • Code review checks for string concatenation or interpolation within database calls
  • Dynamic application testing for unexpected database behavior across input boundaries
  • Web application firewall or API policy rules that monitor suspicious requests to the affected endpoint
  • Database query monitoring for anomalous reads, writes, errors, or privilege use

Automated security review tools may help identify unsafe query composition, but findings should be validated against the application's data-access design.

Sources

SourceLink
code-projects.orgcode-projects.org/
github.comgithub.com/niaoniaollll/cve/issues/8
vuldb.comvuldb.com/cve/CVE-2026-76762
vuldb.comvuldb.com/submit/878975
vuldb.comvuldb.com/vuln/393235
vuldb.comvuldb.com/vuln/393235/cti

Frequently asked

questions

Yes. The affected functionality is described as remotely reachable, although network exposure, authentication, and authorization controls may limit who can access it.

Not necessarily. The required access depends on how /welcome.php is deployed and whether the vulnerable functionality is protected by authentication or other access controls.

Replace dynamically composed SQL with parameterized queries or prepared statements, and use strict input validation as a secondary defense.

Establish secure database-access standards, review request-to-query data flows, apply least-privilege database permissions, and include injection testing in development and deployment checks.

Find out what's already
exploitable in your codebase.