CSRF in Redaxo Core
CVE-2026-117536
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.
Vulnerability class: CSRF (Cross-Site Request Forgery)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 8.8 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
Weakness classification (CWE)
References
- github.com/redaxo/core/security/advisories/GHSA-mrrj-4f5x-j958 (vendor-advisory)
- www.vulncheck.com/advisories/redaxo-before-5.21.3-csrf-token-bypass-via-users-u… (third-party-advisory)
Frequently asked questions
- What is CVE-2026-117536?
- CVE-2026-117536 is a high-severity vulnerability in Redaxo Core, classified under Cross-Site Request Forgery (CSRF). CVSS score: 8.8/10. Published 2026-10-27.
- How severe is CVE-2026-117536?
- High severity. CVSS v3 base score is 8.8 out of 10.