Quick answers
- Is CVE-2026-116824 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116824 being exploited in the wild.
- How severe is CVE-2026-116824?
- 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-116824?
- 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-116824 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-116824?
- 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 referrers_sites.php handler fails to HTML-escape the hostname extracted from stored referrer URLs before rendering it into HTML anchor tags, while the sibling referrers.php handler correctly applies htmlspecialchars() to the same data. An unauthenticated attacker sends a single HTTP request with a crafted Referer header containing HTML metacharacters (e.g., "http://"><img src=x onerror=alert(1)>x.com/poc) that bypasses the scheme validation and is stored unescaped; the payload then executes in the browser of any user visiting the referrer-sites page, persisting for up to 24 days and enabling same-origin XHR/fetch requests to perform authenticated actions.
Affected products
- YesWiki YesWiki before 4.7.0
Timeline
- 2026-10-12: disclosed
- 2026-10-27: advisory