Quick answers
- Is CVE-2026-116899 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116899 being exploited in the wild.
- How severe is CVE-2026-116899?
- Medium severity, with a CVSS score of 6.5, published 27 October 2026.
- Which products and versions are affected?
- REDAXO Core before 5.21.4.
- Is there a fix for CVE-2026-116899?
- Yes: fixed in 5.21.4. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116899 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-116899?
- 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
Technical details
The vulnerability is a broken access control in slice operations: the permission check validates the editor's access to an article, but the actual mutation acts on a slice ID that may belong to a different article in an unauthorized category. The affected code paths include content/edit (delete and edit functions), content_slice_status API, and content_move_slice API. Exploitation requires authentication with content edit permissions on at least one category, and some operations require matching module/template configuration; no user interaction or cross-site vector is needed.
Affected products
- REDAXO core before 5.21.4
Timeline
- 2026-08-03: disclosed
- 2026-10-27: advisory