REDAXO before 5.21.3 CSRF Token Bypass via users/users Privilege Escalation
Impact
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.
Source excerpt · VulnCheckREDAXO 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.
Affected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
redaxo · core
Other versions: unaffected
| Version / range | Source status |
|---|---|
| 0 to before 5.21.3 | affected |
| 5.21.3 | unaffected |
Original source 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.