/

CVE-2026-67689

Severity:

CRITICAL RISK

(9.8)

SQL Injection (CWE-89) in FineAdmin Pagination Endpoints

CVE-2026-67689

Received

Vulnerability type

Category:

SQL Injection

CWE:

CWE-89

Impact:

Unauthorized database access and potential code execution

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

A critical SQL injection vulnerability in FineAdmin V1.0 affects paginated list endpoints that process the field and order parameters. A remote attacker may manipulate database queries without valid authorization, potentially accessing, modifying, or deleting data and, in some database configurations, triggering further code execution.

Affected context

The vulnerability occurs in FineAdmin V1.0 deployments exposing paginated list endpoints that incorporate the field or order request parameters into database queries. Risk is greater when these values are accepted from remote clients without strict allowlisting, parameterization, or equivalent query-construction safeguards.

Exploit preconditions

  • Attack surface: Remote HTTP-accessible paginated list endpoints
  • Required access: Network access to an affected endpoint; authentication requirements depend on the deployment
  • Trigger point: Processing of attacker-controlled field or order parameters
  • Why exploitation is possible: User-controlled values may influence SQL query construction without adequate separation between data and executable query syntax

Why this happens

The underlying bug is the incorporation of untrusted request parameters into SQL statements without consistently using parameterized queries or strict server-side allowlists. This permits an attacker to alter the intended query structure rather than supplying only a column name or sort direction. The issue maps to CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection').

Potential impact

  • An attacker may read sensitive database records
  • An attacker could modify or delete application data
  • Authentication or authorization data may be exposed or altered
  • The application may experience data integrity loss or service disruption
  • Database-specific capabilities could allow further command or code execution
  • Compromised data may support lateral movement into connected systems

General mitigation guidance

Mitigation generally focuses on separating query data from query structure and reducing trust in client-controlled sorting parameters.

Common defensive patterns include:

  • Use parameterized queries or trusted query-builder abstractions for all database values
  • Enforce strict server-side allowlists for sortable fields and sort directions
  • Reject unexpected, duplicated, or malformed pagination parameters
  • Apply least-privilege permissions to application database accounts
  • Avoid exposing database errors or query details in responses
  • Add centralized validation and authorization controls around list endpoints
  • Treat database-specific command or extension features as disabled unless required

How teams detect issues like this

Organizations commonly detect SQL injection risks through:

  • Static analysis rules identifying string concatenation or interpolation in SQL construction
  • Code review checks for request parameters used as column names, ordering clauses, or query fragments
  • Dynamic testing of pagination and sorting parameters using safe test inputs
  • Web application firewall or API gateway policies for anomalous SQL syntax patterns
  • Database monitoring for unexpected query shapes, privilege use, and unusual access volumes
  • Automated security review tools that flag unparameterized database operations

Sources

SourceLink
github.comgithub.com/qflksheep/CVE-2026-67689-FineAdmin.Mvc-vulnerability/blob/main/CVE-2026-67689-ORDER%20BY%20Clause%20SQL%20Injection
github.comgithub.com/qflksheep/FineAdmin.Mvc-ORDER-BY-Clause-SQL-Injection/blob/main/README.md

Frequently asked

questions

Yes. It may be remotely exploitable when an attacker can reach an affected paginated list endpoint and influence the field or order parameters.

Not necessarily. The required access depends on endpoint exposure and application authorization controls; publicly accessible endpoints present the greatest risk.

Use parameterized database operations and map client-provided sorting values to a fixed server-side allowlist rather than embedding them directly into queries.

Combine secure query APIs, strict input validation, least-privilege database accounts, focused code review, automated analysis, and monitoring for abnormal database activity.

Find out what's already
exploitable in your codebase.