GIVE YOUR AGENT THE EVIDENCE

Set up in your agent.

One prompt to get started. Paste it into your coding agent to connect cve.new through MCP and bring vulnerability context into your workflow.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

GIVE YOUR AGENT THE EVIDENCE

Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

GHSA-4f5f-j737-pm58medium4.3

REDAXO: Unwhitelisted ORDER BY Column in rex_list Allows Authenticated Column Enumeration

Check your stack

The advisory, in context

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=asc

Response 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=asc

Users 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;
}

Affected packages

Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.

Ecosystem versions

Earlier releases before 5.21.2

Fixed in 5.21.2

44 explicitly affected versions

5.10.0, 5.10.0-beta1, 5.10.0-beta2, 5.10.1, 5.11.0, 5.11.0-beta1, 5.11.1, 5.11.2, 5.12.0, 5.12.0-beta1, 5.12.0-beta2, 5.12.0-beta3, 5.12.1, 5.13.0, 5.13.0-beta1, 5.13.0-beta2, 5.13.1, 5.13.2, 5.13.3, 5.14.0, 5.14.0-beta1, 5.14.0-beta2, 5.14.1, 5.14.2, 5.14.3, 5.15.0, 5.15.0-beta1, 5.15.1, 5.16.0, 5.16.0-beta1, 5.16.1, 5.17.0, 5.17.1, 5.18.0, 5.18.1, 5.18.2, 5.18.3, 5.19.0, 5.20.0, 5.20.1, 5.20.2, 5.21.0, 5.21.0-beta1, 5.21.1

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "0"
        },
        {
          "fixed": "5.21.2"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "5.10.0",
    "5.10.0-beta1",
    "5.10.0-beta2",
    "5.10.1",
    "5.11.0",
    "5.11.0-beta1",
    "5.11.1",
    "5.11.2",
    "5.12.0",
    "5.12.0-beta1",
    "5.12.0-beta2",
    "5.12.0-beta3",
    "5.12.1",
    "5.13.0",
    "5.13.0-beta1",
    "5.13.0-beta2",
    "5.13.1",
    "5.13.2",
    "5.13.3",
    "5.14.0",
    "5.14.0-beta1",
    "5.14.0-beta2",
    "5.14.1",
    "5.14.2",
    "5.14.3",
    "5.15.0",
    "5.15.0-beta1",
    "5.15.1",
    "5.16.0",
    "5.16.0-beta1",
    "5.16.1",
    "5.17.0",
    "5.17.1",
    "5.18.0",
    "5.18.1",
    "5.18.2",
    "5.18.3",
    "5.19.0",
    "5.20.0",
    "5.20.1",
    "5.20.2",
    "5.21.0",
    "5.21.0-beta1",
    "5.21.1"
  ]
}

References