Description
REDAXO before 5.21.3 contains a cross-site request forgery vulnerability in the backend user administration page (users/users) because the CSRF token check only runs when the save parameter is set, while the update path triggered by FUNC_UPDATE does not require it. Attackers can lure a logged-in backend user with the users[] permission to a crafted GET link to grant administrator rights, deactivate accounts, or lock out the sole administrator.
Published: 2026-10-27
Score: 8.6 High
EPSS: n/a
KEV: No
Impact: Privilege Escalation through CSRF token bypass
Action: Immediate Patch
AI Analysis

Impact

This vulnerability allows attackers to bypass the CSRF token check on the REDAXO backend user administration page when the save parameter is omitted, enabling a crafted GET request to trigger privilege escalation. An attacker can luring a logged‑in backend user with users[] permission to a malicious link to grant themselves administrator rights, deactivate other accounts, or lock out the sole administrator. As a result, the confidentiality, integrity, and availability of the system are compromised through unauthorized account control.

Affected Systems

The flaw affects REDAXO Core versions prior to 5.21.3. Existing installations that have not been updated to 5.21.3 or later are vulnerable. No specific sub‑components or third‑party plugins are noted as affected, so the core backend user administration functionality is the primary target.

Risk and Exploitability

The CVSS score of 8.6 indicates high severity, and although the EPSS score is not publicly available, the exploitation path requires only a crafted link and a logged‑in user, which is a realistic scenario in many deployments. The vulnerability is not listed in the CISA KEV catalog, but the described attack vector relies on CSRF and does not require network exposure beyond the victim's browser. Consequently, the risk remains significant, especially in environments where backend users have broad permissions.

Generated by OpenCVE AI on October 27, 2026 at 12:26 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to REDAXO 5.21.3 or later, which fixes the CSRF token check in users/users.
  • Restrict the users[] permission to administrators only to limit the scope of potential privilege escalation.
  • Verify that all backend endpoints enforce CSRF token validation regardless of the presence of the save parameter.

Generated by OpenCVE AI on October 27, 2026 at 12:26 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 27 Oct 2026 11:15:00 +0000

Type Values Removed Values Added
Description REDAXO before 5.21.3 contains a cross-site request forgery vulnerability in the backend user administration page (users/users) because the CSRF token check only runs when the save parameter is set, while the update path triggered by FUNC_UPDATE does not require it. Attackers can lure a logged-in backend user with the users[] permission to a crafted GET link to grant administrator rights, deactivate accounts, or lock out the sole administrator.
Title REDAXO before 5.21.3 CSRF Token Bypass via users/users Privilege Escalation
First Time appeared Redaxo
Redaxo redaxo
Weaknesses CWE-352
CPEs cpe:2.3:a:redaxo:redaxo:*:*:*:*:*:*:*:*
Vendors & Products Redaxo
Redaxo redaxo
References
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 8.6, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-10-27T10:59:31.445Z

Reserved: 2026-10-27T10:33:39.045Z

Link: CVE-2026-117536

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-27T11:17:34.200

Modified: 2026-10-27T11:17:34.200

Link: CVE-2026-117536

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-27T12:30:02Z

Weaknesses
  • CWE-352

    Cross-Site Request Forgery (CSRF)