Quick answers
- Is CVE-2026-105224 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105224 being exploited in the wild.
- How severe is CVE-2026-105224?
- Medium severity, with a CVSS score of 5.4, published 4 October 2026.
- Which products and versions are affected?
- YesWiki before 4.6.7.
- Is there a fix for CVE-2026-105224?
- Yes: fixed in 4.6.7. Until then: Restrict page editing permissions to trusted users only, and review existing page edits for malicious {{valeur}} action usage pointing to untrusted or internal URLs. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-105224 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-105224?
- 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.6.7
Restrict page editing permissions to trusted users only, and review existing page edits for malicious {{valeur}} action usage pointing to untrusted or internal URLs.
Technical details
The valeur action in tools/bazar/actions/valeur.php accepts a URL parameter from wiki markup, appends /html to it, fetches the content server-side via file_get_contents(), and echoes extracted HTML fragments without escaping. This enables both SSRF (Server-Side Request Forgery) to probe internal networks and XSS via unescaped remote content injection. A page editor can inject img onerror handlers or other JavaScript via attacker-controlled endpoints, and the absence of URL scheme/host allowlists, private-network blocking, or output sanitization allows full exploitation.
Affected products
- YesWiki YesWiki before 4.6.7
Timeline
- 2026-09-01: disclosed
- 2026-07-14: patched: Fix committed via GHSA-6rvf-7pwm-6j44