CVE-2026-116211 YesWiki 4.5.0 before 4.7.0 SQL Injection via date_maj_fiche in Bazar entry create
High 8.8
Published
Updated
Check this codebase for CVE-2026-116211 and fix it if it is affected.
What it is: CVE-2026-116211 is a high-severity vulnerability in yeswiki, published on 25 Oct 2026.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-116211 exists.
Affected product: yeswiki. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-116211/ (Markdown: https://insights.sbomify.com/CVE-2026-116211/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-116211?
CVE-2026-116211 is a high-severity vulnerability in yeswiki, published on 25 Oct 2026.
Official description
YesWiki 4.5.0 before 4.7.0 contains an SQL injection vulnerability in PageManager::save(), where the date_maj_fiche field of a Bazar entry-creation request is concatenated unescaped into an INSERT statement. Unauthenticated attackers on default installs can inject a sub-SELECT against wiki_users to exfiltrate password hashes.
Weakness: CWE-89
Which versions are affected by CVE-2026-116211?
How do I fix CVE-2026-116211?
No fix has been published for CVE-2026-116211 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-116211 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-116211 exists.
Sources
Also known as GHSA-c22v-7hq8-8gqq, GHSA-wjf7-hrf3-9gcx.