Quick answers
- Is CVE-2026-116823 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116823 being exploited in the wild.
- How severe is CVE-2026-116823?
- Medium severity, with a CVSS score of 6.1, published 27 October 2026.
- Which products and versions are affected?
- YesWiki before 4.7.0.
- Is there a fix for CVE-2026-116823?
- Yes: fixed in 4.7.0. Until then: Remove or restrict the $_REQUEST fallback in BazarField::getValue() to prevent unsanitized query parameters from reaching Twig templates with the |raw filter enabled. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116823 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-116823?
- Check whether you run YesWiki 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: 4.7.0
Remove or restrict the $_REQUEST fallback in BazarField::getValue() to prevent unsanitized query parameters from reaching Twig templates with the |raw filter enabled.
Technical details
BazarField::getValue() in tools/bazar/fields/BazarField.php falls back to reading unsanitized $_REQUEST values when an entry's stored JSON lacks a field key. These values are rendered through Twig templates with the |raw filter enabled, which bypasses auto-escaping. An unauthenticated attacker can craft a URL with a query parameter matching a missing Bazar field name to inject reflected JavaScript that executes in the victim's browser.
Affected products
- YesWiki YesWiki before 4.7.0
Timeline
- 2026-10-12: disclosed
- 2026-10-27: advisory