CVE-2026-117536: high-severity vulnerability in redaxo core
REDAXO before 5.21.3 CSRF Token Bypass via users/users Privilege Escalation
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.6epss 0.1%
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.
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
Affected products
redaxo · coreRelated CVEs — redaxo core
In the same product, most dangerous first.
CVE-2026-117532CRITICALREDAXO Core 5.3.0 before 5.21.4 Authentication Bypass via History PluginEPSS 0.7%CVE-2026-53599HIGHRedaxo has a Mediapool isAllowedExtension bypass via multi-segment filename that leads to authenticated RCE on Apache mod_php multi-extension handlersEPSS 0.5%CVE-2026-62998MEDIUMREDAXO: Unwhitelisted ORDER BY Column in rex_list Allows Authenticated Column EnumerationEPSS 0.4%CVE-2026-116893MEDIUMREDAXO core before 5.21.5 Missing Authorization in rex_api_package APIEPSS 0.3%CVE-2026-116896HIGHREDAXO before 5.21.5 Privilege Escalation via Backup Export of Authentication TablesEPSS 0.2%CVE-2026-116897HIGHREDAXO before 5.21.4 Missing Authorization in Version and History PreviewsEPSS 0.2%