Quick answers
- Is CVE-2026-116202 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116202 being exploited in the wild.
- How severe is CVE-2026-116202?
- Medium severity, with a CVSS score of 5.4, published 25 October 2026.
- Which products and versions are affected?
- YesWiki before 4.7.0.
- Is there a fix for CVE-2026-116202?
- Yes: fixed in 4.7.0. Until then: Restrict file upload permissions for authenticated users, or disable SVG uploads in the bazar ImageField configuration by removing 'svg' from the attach_config.ext_images list until upgrading to version 4.7.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116202 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-116202?
- 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
Restrict file upload permissions for authenticated users, or disable SVG uploads in the bazar ImageField configuration by removing 'svg' from the attach_config.ext_images list until upgrading to version 4.7.0.
Technical details
The ImageField class in YesWiki's bazar component fails to sanitize uploaded SVG files before storing them, even though a sibling FileField class was patched in v4.6.7. SVG files are included in the default image extensions list and are served with Content-Type: image/svg+xml, allowing embedded JavaScript to execute. An authenticated user can submit a malicious SVG via the entries API, which gets stored and executed for all subsequent viewers.
Affected products
- YesWiki YesWiki before 4.7.0
Timeline
- 2026-10-09: disclosed
- 2026-10-25: advisory