Quick answers
- Is CVE-2026-116211 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116211 being exploited in the wild.
- How severe is CVE-2026-116211?
- High severity, with a CVSS score of 8.2, published 25 October 2026.
- Which products and versions are affected?
- YesWiki 4.5.0 before 4.7.0.
- Is there a fix for CVE-2026-116211?
- 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-116211 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-116211?
- 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 exists in PageManager::save() where the attacker-controlled date_maj_fiche parameter is concatenated unescaped into a MySQL INSERT statement, unlike all sibling column values which are properly escaped via mysqli_real_escape_string(). An unauthenticated attacker can break out of the quoted time literal by injecting a double-quote and supply a sub-SELECT to exfiltrate password hashes from wiki_users, or perform blind time-based SQL injection. The default configuration (bazarIgnoreAcls:true, use_captcha:false) allows exploitation via the public Bazar entry form without authentication.
Affected products
- YesWiki YesWiki 4.5.0 before 4.7.0
Timeline
- 2026-10-09: disclosed
- 2026-10-25: advisory