Quick answers
- Is CVE-2026-117532 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-117532 being exploited in the wild.
- How severe is CVE-2026-117532?
- Critical severity, with a CVSS score of 9.8, published 27 October 2026.
- Which products and versions are affected?
- REDAXO Core 5.3.0 to 5.21.3.
- Is there a fix for CVE-2026-117532?
- Yes: fixed in 5.21.4. Until then: Deactivate the structure/history plugin if the history viewing feature is not required, or apply the provided one-line code change to redaxo/src/addons/structure/plugins/history/boot.php (line 16) to disable the temporary login mechanism while preserving history snapshots. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-117532 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-117532?
- Check whether you run REDAXO Core at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 5.21.4
Deactivate the structure/history plugin if the history viewing feature is not required, or apply the provided one-line code change to redaxo/src/addons/structure/plugins/history/boot.php (line 16) to disable the temporary login mechanism while preserving history snapshots.
Technical details
The history plugin's temporary frontend login feature derives authorization tokens from a login name, timestamp, and session-tied secret, but the secret can be forced into a predictable state without prior authentication. This allows unauthenticated attackers to forge valid tokens for any known account (commonly "admin") to gain a backend session. The vulnerability has a network attack vector with no privileges required and no user interaction; exploitation enables arbitrary code execution via templates and modules on non-live installations.
Affected products
- REDAXO core 5.3.0 to 5.21.3
Timeline
- 2026-08-03: disclosed
- 2026-10-27: advisory