All vulnerabilities

Servers and applications

GHSA-mrrj-4f5x-j958

CSRF token check bypass in the user administration allows privilege escalation

Severity
High 8.6
Published
31 Jul 2026
Last changed
31 Jul 2026
Added to UpHeron
3 Nov 2026
Fixed in
5.21.3
Weakness
Improper privilege management (CWE-269)Cross-site request forgery (CWE-352)
Attack
Over the network · No login needed · Needs someone to click or open something
Attacker can
Read data · Change data · Take it down
CVSS 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
Sources
Project advisories (GitHub)

Description

The backend user administration (page=users/users) ran its CSRF check behind a condition that the write path itself did not share. A request could therefore reach the update path without a valid token.

The attack works as a plain GET request, so it was enough for a backend user with the users[] permission to open an attacker-controlled page while logged in. Depending on the parameters, this modified arbitrary user accounts — granting administrator rights, deactivating accounts, or locking the only administrator out of the backend.

Saving a user in the backend covers three write paths: create, update and delete. The CSRF check for the create and update paths was bound to an additional condition — it only ran when the save parameter was truthy and one of the function actions was requested:

The update itself, however, was triggered by FUNC_UPDATE or FUNC_APPLY alone and did not require save:

From redaxo/core's security advisory. Shortened; the full text is there.

Affected software

SoftwareAffected versions
REDAXOServers and applications · github:redaxo/core
  • Every version before 5.21.3

About REDAXO

Content management system

From Wikidata, CC0 1.0.
GitHub stars
356GitHub, 15 Nov 2026
Forks
115GitHub, 15 Nov 2026
Latest release
5.21.6GitHub, 15 Nov 2026
Released
25 Oct 2026GitHub
License
MIT LicenseWikidata
Written in
PHPWikidata
First published on GitHub
4 Jul 2010GitHub

References