Is CVE-2026-116205 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-116205 being exploited in the wild.

How severe is CVE-2026-116205?

Medium severity, with a CVSS score of 5.3, published 25 October 2026.

Is there a fix for CVE-2026-116205?

Yes: fixed in 4.7.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-116205 attacked?

It is attacked over the network.

Am I affected by CVE-2026-116205?

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.

CVE-2026-116205: YesWiki server-side request forgery in page render handler

CVE-2026-116205 · Severity: medium · CVSS 5.3 · Published 2026-10-25

YesWiki is a collaborative wiki platform that allows users to create and edit web pages. An unauthenticated attacker can exploit a flaw in the page rendering feature to force the server to make HTTP requests to internal systems and services that should not be accessible from the internet, then read the responses back. This could expose sensitive data from internal databases, configuration systems, or other services running behind the organization's firewall.

Technologies: YesWiki. Vendors: YesWiki.

Quick answers

Is CVE-2026-116205 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-116205 being exploited in the wild.
How severe is CVE-2026-116205?: Medium severity, with a CVSS score of 5.3, published 25 October 2026.
Which products and versions are affected?: YesWiki before 4.7.0.
Is there a fix for CVE-2026-116205?: Yes: fixed in 4.7.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-116205 attacked?: It is attacked over the network.
Am I affected by CVE-2026-116205?: 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

Technical details

The vulnerability is an unauthenticated server-side request forgery (SSRF) in the page render handler that processes the [[|URL]] wiki syntax without validating the target URL. The flaw exists in formatters/wakka.php and raw.php, which use PHP's file() function to fetch and echo back arbitrary URLs when a user supplies [[|URL]] syntax in the content parameter. The vulnerability is reachable both pre-authentication via the /render handler and post-authentication through stored wiki content, with no ACL checks protecting the render gateway.

Affected products

YesWiki YesWiki before 4.7.0

Timeline

2026-10-09: disclosed
2026-10-25: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.