/

CVE-2026-90879

Severity:

HIGH RISK

(7.3)

SQL Injection (CWE-89) in FilePress Publish Module

CVE-2026-90879

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 affects the Publish Module in zyx0814 FilePress through the orderby and order parameters in dzz/publish/search.php.

A remote attacker may manipulate these inputs to alter database queries, potentially exposing, changing, or disrupting application data when the affected endpoint is accessible.

Affected context

The vulnerability occurs in FilePress deployments using the Publish Module and exposing the affected search functionality. It becomes risky when the orderby or order parameters are incorporated into database queries without sufficient validation, normalization, or safe query construction.

Exploit preconditions

  • Attack surface: A remotely accessible Publish Module search endpoint
  • Required access: Access sufficient to submit requests to the affected functionality; authentication requirements may vary by deployment
  • Trigger point: Processing of the orderby or order request parameters in dzz/publish/search.php
  • Why exploitation is possible: Attacker-controlled input may influence SQL query construction without adequate allowlisting or parameter-safe handling

Why this happens

The underlying bug is an injection flaw in which externally supplied sorting-related parameters are treated as trusted components of a database query. If query structure is assembled from these values without strict validation and safe database APIs, an attacker may influence SQL interpretation.

This maps primarily to CWE-89: Improper Neutralization of Special Elements used in an SQL Command (SQL Injection). It is also related to CWE-74, which covers improper neutralization of special elements in output used by downstream interpreters.

Potential impact

  • An attacker may read unauthorized database records
  • Sensitive application or user information could be exposed
  • Database contents may be modified or deleted
  • The application could experience service disruption
  • Compromised data could support further attacks against connected systems

General mitigation guidance

Mitigation generally focuses on ensuring that request parameters cannot control SQL syntax.

Common defensive patterns include:

  • Using parameterized queries or prepared statements for database values
  • Applying strict allowlists for sortable fields and permitted sort directions
  • Mapping external parameter names to fixed, server-side query fragments
  • Avoiding direct concatenation of request data into SQL statements
  • Enforcing least-privilege database accounts with only required permissions
  • Separating database credentials and limiting access to sensitive tables
  • Treating authentication and authorization as independent controls from input validation

How teams detect issues like this

Organizations can assess for this issue through:

  • Static analysis rules that flag string concatenation or interpolation in SQL construction
  • Code review checks for request parameters used in ORDER BY, filtering, or query fragments
  • Dynamic testing of sorting and search parameters using non-destructive injection test cases
  • Web application firewall or API policy rules monitoring anomalous database-oriented input
  • Database audit logs for unexpected query structure, access patterns, or privilege use
  • Automated security review tools that identify unsafe query-building patterns

Sources

SourceLink
github.comgithub.com/zyx0814/FilePress/
github.comgithub.com/zyx0814/FilePress/issues/74
vuldb.comvuldb.com/cve/CVE-2026-90879
vuldb.comvuldb.com/submit/928834
vuldb.comvuldb.com/vuln/403473
vuldb.comvuldb.com/vuln/403473/cti

Frequently asked

questions

Yes. The described attack can be launched remotely when the affected Publish Module endpoint is reachable and accepts attacker-controlled request parameters.

The available information does not establish a universal authentication requirement. Exploitability depends on whether the endpoint is public, what access controls are enabled, and which users can reach it.

Use parameterized database access wherever possible and restrict sortable columns and directions to fixed server-side allowlists rather than accepting arbitrary query fragments.

Combine secure query APIs, strict input validation, least-privilege database accounts, code review, automated analysis, and monitoring of database query anomalies.

Find out what's already
exploitable in your codebase.