Quick answers
- Is CVE-2026-117537 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-117537 being exploited in the wild.
- How severe is CVE-2026-117537?
- Medium severity, with a CVSS score of 4.1, published 27 October 2026.
- Which products and versions are affected?
- REDAXO before 5.21.0.
- Is there a fix for CVE-2026-117537?
- Yes: fixed in 5.21.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-117537 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-117537?
- 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.0
Technical details
The type parameter in the metainfo_default_fields_create API is concatenated unsanitized into an exception message, which is then rendered by rex_view::message() without HTML escaping. An authenticated attacker with backend access and possession of a valid CSRF token can inject arbitrary HTML and JavaScript into the error message. The vulnerability requires an authenticated backend session and CSRF token, but no user interaction is needed beyond opening a crafted link; however, the impact is limited to the attacker's own session if they trigger it themselves.
Affected products
- REDAXO REDAXO before 5.21.0
Timeline
- 2026-04-09: disclosed
- 2026-10-27: advisory