CVE-2026-62998: REDAXO: Unwhitelisted ORDER BY Column in rex_list Allows Authenticated Column Enumeration
Summary The rexlist component reads the SQL sort column directly from the sort GET parameter without validating it against the set of columns declared sortable via setColumnSortable(). Although the value is wrapped in backticks via escapeIdentifier() (preventing classical SQL injection), this still allows any authenticated backend user to ORDER BY any column in the query's FROM tables, including unselected sensitive…
Published Sep 24, 2026
Affected packages
redaxo/source
- Ecosystem
- Composer (PHP)
- Affected
- <= 5.21.1
- Fixed in
- 5.21.2
- Check
composer show redaxo/source
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
The rex_list component reads the SQL sort column directly from the sort GET parameter without validating it against the set of columns declared sortable via setColumnSortable(). Although the value is wrapped in backticks via escapeIdentifier() (preventing classical SQL injection), this still allows any authenticated backend user to ORDER BY any column in the query's FROM tables, including unselected sensitive columns such as password from the rex_user table, and perform error-based column enumeration.
Details
File: redaxo/src/core/lib/list.php:976-982 — getSortColumn() returns the raw request parameter without whitelist check:
public function getSortColumn($default = null)
{
if (rex_request('list', 'string') == $this->getName()) {
return rex_request('sort', 'string', $default); // NO validation against sortable columns
}
return $default;
}File: redaxo/src/core/lib/list.php:899-911 — prepareQuery() uses it directly in the ORDER BY clause:
protected function prepareQuery($query, array $defaultSort = [])
{
$sortColumn = $this->getSortColumn();
if ('' != $sortColumn) {
$sql = rex_sql::factory($this->db);
$sortColumn = $sql->escapeIdentifier($sortColumn); // backtick-wraps, but no whitelist
if ($defaultSort || false === stripos($query, ' ORDER BY ')) {
$query .= ' ORDER BY ' . $sortColumn . ' ' . $sortType;
}
}The users list queries rex_user which contains password, previous_passwords, password_change_required — not in the SELECT. Specifying a non-existent column name produces a MySQL Unknown column exception whose message is propagated to the user, confirming or denying column existence.
PoC
Column enumeration (error-based):
GET /redaxo/index.php?page=users&list=<list_name>&sort=nonexistent_col&sorttype=ascResponse will contain: Unknown column 'nonexistent_col' in 'order clause'
Sort by password hash (data ordering leak):
GET /redaxo/index.php?page=users&list=<list_name>&sort=password&sorttype=ascUsers are silently reordered by their Argon2 password hash.
Impact
Authenticated backend users (non-admin) can enumerate database column names of internal tables via error messages and manipulate query ordering to include sensitive unselected columns. While this does not allow arbitrary SQL execution due to backtick escaping, it constitutes an information disclosure vulnerability enabling targeted further attacks.
Fix
Validate the sort request parameter against the whitelist of columns registered with setColumnSortable() before use in the query:
public function getSortColumn($default = null)
{
if (rex_request('list', 'string') == $this->getName()) {
$requested = rex_request('sort', 'string', $default);
if ($requested !== null && $this->hasColumnOption($requested, REX_LIST_OPT_SORT)) {
return $requested;
}
}
return $default;
}Credited to de3erve-hunter.
References
- https://github.com/redaxo/core/security/advisories/GHSA-4f5f-j737-pm58
- https://nvd.nist.gov/vuln/detail/CVE-2026-62998
- https://github.com/redaxo/core/pull/6580
- https://github.com/redaxo/core/commit/c44ba5206a28427984100c994010f2aaa6703efd
- https://github.com/redaxo/core/releases/tag/5.21.2
- https://github.com/advisories/GHSA-4f5f-j737-pm58
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-63000
REDAXO: Missing CSRF Protection on Package Update Action Allows Forced Addon Updates
medium6.4Sep 23, 2026CVE-2026-63001
REDAXO: Stored XSS via Unescaped Media Manager Type Name in `mediaIsInUse()`
medium4.8Sep 23, 2026CVE-2026-63002
REDAXO: Stored XSS in Mediapool Sync Page via Unescaped Filesystem Filenames
medium4.8Sep 23, 2026CVE-2026-53599
Redaxo has a Mediapool isAllowedExtension bypass via multi-segment filename that leads to authenticated RCE on Apache mod_php multi-extension handlers
high7.5Jul 31, 2026GHSA-m662-8jrj-cw6v
REDAXO has reflected XSS in backend Metainfo API via type parameter (CSRF token required)
low2.1Apr 10, 2026GHSA-xq4j-g85q-wf97
REDAXO has reflected XSS backend packages API via function parameter (CSRF token required)
low2.1Apr 10, 2026
