/

CVE-2026-79569

Severity:

CRITICAL RISK

(9.8)

SQL Injection (CWE-89) in Movie_Recommend /loadingmore

CVE-2026-79569

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-89

Impact:

Sensitive Information Disclosure and Database Compromise

Severity:

CRITICAL RISK

(9.8)

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

Movie_Recommend v1.0.0 contains a SQL injection vulnerability in the sort parameter of the /loadingmore endpoint. An attacker who can submit requests to this endpoint may manipulate database queries to access sensitive information, particularly where user-controlled sorting input is incorporated into SQL without safe handling.

Affected context

The vulnerability occurs in Movie_Recommend v1.0.0 when the /loadingmore endpoint processes the sort parameter. Risk is greatest when the endpoint is publicly reachable or available to low-privileged users and the parameter is used to construct database queries without strict allowlisting, parameter binding, or equivalent query-safe handling.

Exploit preconditions

  • Attack surface: The HTTP /loadingmore endpoint and its sort parameter. - Required access: The ability to send requests to the affected endpoint;

authentication requirements depend on the deployment configuration.

  • Trigger point: Server-side processing of a crafted sort parameter. - Why exploitation is possible: Input may influence SQL statement structure

rather than being treated solely as a constrained sorting value.

Why this happens

The underlying bug is improper neutralization of special elements in user-controlled SQL input, which maps to CWE-89: Improper Neutralization of Special Elements used in an SQL Command (SQL Injection). The insecure pattern occurs when request data is concatenated into query text or otherwise allowed to affect SQL syntax without parameterization, strict allowlisting, or a safe query-building abstraction.

Potential impact

  • An attacker may retrieve sensitive database records.
  • An attacker could bypass intended query restrictions or authorization boundaries.
  • Database contents may be altered or deleted if the database account permits it.
  • The application may suffer data exposure, integrity loss, or service disruption.
  • Compromised database credentials or connected systems could increase the impact.

General mitigation guidance

Mitigation generally centers on separating data from SQL structure and reducing trust in request parameters. Common defensive patterns include using parameterized queries or vetted query builders, allowlisting sorting fields and directions, rejecting unexpected values before query construction, and avoiding direct concatenation of request data into SQL. Database accounts can be limited to the privileges required by the application, while sensitive records and error details can be minimized in responses. Independent authorization checks and secure-by-default endpoint behavior further reduce exposure.

How teams detect issues like this

Detection can include static analysis for string concatenation or formatting of request parameters into SQL, code review checks for dynamic ORDER BY or sorting clauses, and tests that verify all accepted sort values are mapped from a fixed server-side list. Runtime monitoring can flag anomalous request patterns, database errors, unusual query shapes, and unexpected data-access volume. Web application firewalls, database activity monitoring, and automated security review tools may provide additional coverage when tuned to the application's normal behavior.

Sources

SourceLink
github.comgithub.com/fangtang7/CVE/blob/main/movie/sql.md

Frequently asked

questions

It may be remotely exploitable when the /loadingmore endpoint is network-accessible and accepts requests from an attacker. Authentication, routing, and other deployment controls determine the practical scope.

The attacker needs the ability to reach the endpoint and influence the sort parameter. This may require an account if the application protects the endpoint, but the specific access requirement depends on deployment settings.

Use parameterized queries for data values and map sorting options through a strict server-side allowlist rather than inserting raw request values into SQL structure.

Apply secure query APIs consistently, review dynamic query construction, enforce least-privilege database accounts, validate inputs at trust boundaries, and test endpoint parameters for injection behavior during development and security assessment.

Find out what's already
exploitable in your codebase.