Quick answers
- Is CVE-2026-116206 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116206 being exploited in the wild.
- How severe is CVE-2026-116206?
- Medium severity, with a CVSS score of 6.4, published 25 October 2026.
- Which products and versions are affected?
- YesWiki 4.2.0 before 4.7.0.
- Is there a fix for CVE-2026-116206?
- Yes: fixed in 4.7.0. Until then: Disable the allow_raw_html configuration option, or disable the comments feature globally if not essential until upgrading. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116206 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-116206?
- 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
Disable the allow_raw_html configuration option, or disable the comments feature globally if not essential until upgrading.
Technical details
Authenticated users can inject raw HTML and JavaScript via the wakka raw-HTML syntax (""..."") into comment bodies submitted to the /api/comments endpoint. Comments are stored without sanitization and rendered with the Twig |raw filter, which disables output escaping. Because the allow_raw_html option defaults to true, injected scripts execute persistently in every viewer's session, including administrators, enabling session hijacking and privilege escalation.
Affected products
- YesWiki YesWiki 4.2.0 before 4.7.0
Timeline
- 2026-10-09: disclosed
- 2026-10-25: advisory