Skip to content

← Actionable
Medium, CVSS 4.3amended

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

CVE-2026-62998GHSA-4f5f-j737-pm58

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (redaxo/source 5.21.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
EPSS
  • CVE-2026-62998: 0.39% estimated exploitation activity in the next 30 days; percentile 32.94 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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 columns such as password from the rexuser 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: File: redaxo/src/core/lib/list.php:899-911 — prepareQuery() uses it directly in the ORDER BY clause: The users list queries rexuser which contains password, previouspasswords, passwordchangerequired — 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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-4f5f-j737-pm58

  2. Revision 1 · created ·

    Published from osv record GHSA-4f5f-j737-pm58

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-62998

Advisory: REDAXO: Unwhitelisted ORDER BY Column in rex_list Allows Authenticated Column Enumeration
IDs: CVE-2026-62998, GHSA-4f5f-j737-pm58
Record: https://patchnext.com/advisories/cve-2026-62998 (revision 2, source checked 26 Oct 2026, 14:53 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: redaxo/source 5.21.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist redaxo/source: affected <= 5.21.1; fixed in 5.21.2

## Suggested inspection (read-only)
- Packagist redaxo/source: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on redaxo/source.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-4f5f-j737-pm58 (OSV record GHSA-4f5f-j737-pm58 lists affected ranges: Packagist redaxo/source >=0 <5.21.2 (fixed))
- Verified: https://github.com/advisories/GHSA-4f5f-j737-pm58 (GitHub-reviewed advisory GHSA-4f5f-j737-pm58 lists affected ranges: Packagist redaxo/source >=0 <=5.21.1)

Commands are suggestions: review each one before running it.

Loading voting…