/

CVE-2026-90849

Severity:

HIGH RISK

(7.3)

SQL Injection (CWE-89) in College Notes Gallery System

CVE-2026-90849

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-74, CWE-89

Impact:

Database compromise and potential authentication bypass

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 SQL injection vulnerability in the College Notes Gallery Management System may allow remotely supplied input in the login workflow to alter database queries. If the vulnerable User parameter reaches a database query without effective parameterization, an attacker could bypass authentication, access data, or modify database content.

Affected context

The vulnerability occurs in the login functionality exposed through /College/login.php, where the User argument is processed. Risk depends on whether the application constructs database statements from this input without parameterized query handling, and on the database account privileges available to the application.

Exploit preconditions

  • Attack surface: Remotely accessible login endpoint
  • Required access: The ability to send requests to /College/login.php; a pre-existing account may not be required
  • Trigger point: Processing of the User argument during authentication
  • Why exploitation is possible: User-controlled input may be incorporated into a database query without sufficient separation between data and SQL syntax

Why this happens

The underlying issue is an injection flaw in which externally supplied login input can influence the structure or meaning of a SQL statement. This commonly results from string concatenation or interpolation of request values into queries instead of using parameterized statements and controlled database APIs. It 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.

Potential impact

  • An attacker may bypass application authentication
  • Sensitive records could be read or disclosed
  • Database content could be altered or deleted
  • Application availability could be affected
  • Excessive database privileges could increase the scope of compromise

General mitigation guidance

Mitigation generally centers on preventing request data from becoming executable SQL syntax.

Common defensive patterns include:

  • Use parameterized queries or prepared statements for all database operations
  • Apply allowlist-based validation appropriate to the expected user identifier format
  • Keep database credentials separate from application input and configuration
  • Grant the application database account only the minimum required privileges
  • Return generic authentication errors and avoid exposing database details
  • Treat validation as a supplementary control rather than a replacement for query parameterization

How teams detect issues like this

Detection approaches may include:

  • Static analysis rules for string concatenation or interpolation in SQL query construction
  • Code review of authentication handlers and all request-to-database data flows
  • Dynamic testing that uses benign malformed input to identify unexpected query behavior
  • Web application firewall or API gateway policies for suspicious SQL metacharacter patterns
  • Database monitoring for anomalous authentication queries, error rates, and unusual access patterns
  • Automated security review tools that flag unsafe database API usage

Sources

SourceLink
github.comgithub.com/akaiwen/cve/issues/1
vuldb.comvuldb.com/cve/CVE-2026-90849
vuldb.comvuldb.com/submit/926860
vuldb.comvuldb.com/submit/926861
vuldb.comvuldb.com/vuln/403404
vuldb.comvuldb.com/vuln/403404/cti
sourcecodester.comsourcecodester.com/

Frequently asked

questions

Yes. The reported attack surface is the remotely accessible login functionality, although successful exploitation depends on how the application processes the User parameter and connects to its database.

Not necessarily. Because the affected functionality is a login endpoint, an attacker may be able to submit input before authentication; the exact requirement depends on deployment and request controls.

Use parameterized queries or prepared statements so that the User value remains data rather than becoming part of SQL syntax. Apply strict validation and least-privilege database access as supporting controls.

Standardize secure database access APIs, review every request-to-query data flow, test authentication paths for injection behavior, and enforce static analysis and peer-review policies for query construction.

Find out what's already
exploitable in your codebase.