/

CVE-2026-54646

Severity:

HIGH RISK

(7.2)

SQL Injection (CWE-89) in CubeCart Admin Maintenance

CVE-2026-54646

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-89

Impact:

Database confidentiality, integrity, and availability compromise

Severity:

HIGH RISK

(7.2)

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

CubeCart contains a SQL injection vulnerability in its administrator maintenance functionality, where administrator-controlled table names are inserted into database statements without adequate identifier validation or escaping. An authenticated administrator may be able to alter the SQL structure, potentially affecting the confidentiality, integrity, or availability of data within the application's database privileges.

Affected context

The vulnerability occurs in CubeCart versions before 6.7.5 when the administrator maintenance interface processes table-name values for ALTER TABLE, CHECK TABLE, or ANALYZE TABLE operations. Risk is present where an authenticated administrator can submit or influence these values and the application constructs SQL statements without treating table identifiers as strictly controlled database objects.

Exploit preconditions

  • Attack surface: CubeCart administrator maintenance functionality
  • Required access: Authenticated administrator-level access or equivalent ability to submit maintenance parameters
  • Trigger point: Processing of administrator-controlled table-name values in maintenance SQL statements
  • Why exploitation is possible: Table identifiers are placed into SQL statements without sufficient validation or escaping of embedded identifier delimiters, allowing the intended statement structure to be modified

Why this happens

The underlying bug is improper neutralization of special elements in SQL identifiers. The application constructs ALTER TABLE, CHECK TABLE, and ANALYZE TABLE statements using administrator-controlled table-name values, but does not enforce an allowlisted identifier format or safely handle embedded backticks. This behavior maps to CWE-89: Improper Neutralization of Special Elements used in an SQL Command, because input is incorporated into SQL syntax rather than being constrained to a trusted identifier representation.

Potential impact

  • An attacker may read or alter data available through the application's database account.
  • Database structures or maintenance operations could be modified.
  • Application data integrity could be compromised.
  • Database availability could be reduced through disruptive SQL operations.
  • The impact could extend to other application functions sharing the same database privileges.

General mitigation guidance

Mitigation generally focuses on preventing user-controlled values from becoming SQL syntax.

Common defensive patterns include:

  • Restricting table names to a server-side allowlist of known maintenance targets.
  • Validating identifiers against a strict character and format policy before statement construction.
  • Using database APIs or query-building abstractions that safely represent identifiers where supported.
  • Separating identifier selection from ordinary data values and avoiding direct string concatenation.
  • Applying least-privilege permissions to the application's database account.
  • Treating administrator-supplied values as untrusted despite their authenticated source.

How teams detect issues like this

Detection approaches can include:

  • Static analysis for SQL statements assembled through string concatenation with request or form values.
  • Code review checks for dynamic ALTER TABLE, CHECK TABLE, or ANALYZE TABLE construction.
  • Searches for database identifier interpolation without allowlists or dedicated identifier-quoting APIs.
  • Runtime monitoring for unusual maintenance statements or unexpected database schema activity.
  • Policy enforcement requiring parameterization or approved query-construction helpers for database access.
  • Neutral automated code-review tools can help identify untrusted input flows into SQL execution paths.

Sources

SourceLink
github.comgithub.com/cubecart/v6/blob/6.7.5/admin/sources/release_notes/6.7.5.inc.php
github.comgithub.com/cubecart/v6/commit/fc08d55628191969f2345d06d862df316f7d44d3
github.comgithub.com/cubecart/v6/releases/tag/6.7.5
github.comgithub.com/cubecart/v6/security/advisories/GHSA-qcx6-cg43-ffmx

Frequently asked

questions

Exploitation depends on the CubeCart administration interface being reachable and on the attacker having authenticated administrator-level access. It is not generally an unauthenticated public attack.

The relevant access is the ability to invoke the maintenance functionality and control the table-name values processed by it. The exact exposure depends on deployment permissions and administrative access controls.

The safest pattern is to remove user-controlled SQL structure, use a server-side allowlist for permitted table identifiers, and rely on safe database abstractions for any unavoidable dynamic identifiers.

Treat all submitted values as untrusted, apply strict identifier validation, review dynamic SQL paths, monitor database activity, and limit the privileges granted to application database accounts.

Find out what's already
exploitable in your codebase.