Quick answers
- Is CVE-2026-117534 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-117534 being exploited in the wild.
- How severe is CVE-2026-117534?
- Medium severity, with a CVSS score of 5.4, published 27 October 2026.
- Which products and versions are affected?
- REDAXO before 5.21.3.
- Is there a fix for CVE-2026-117534?
- Yes: fixed in 5.21.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-117534 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-117534?
- Check whether you run REDAXO 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.3
Technical details
The article history plugin in REDAXO fails to validate CSRF tokens on two state-changing actions: clearing all history snapshots (func=clearall) and restoring article snapshots (rex_history_function=snap). Both actions process GET requests via $_REQUEST without token validation, and REDAXO's default SameSite=Lax cookie policy allows cross-site GET requests to carry the victim's session cookie. An attacker needs only to lure a logged-in backend user to a malicious page; no user interaction beyond navigation is required.
Affected products
- REDAXO REDAXO before 5.21.3
Timeline
- 2026-07-31: disclosed
- 2026-10-27: advisory