# CVE-2026-116207: YesWiki 4.6.0 before 4.7.0 SQL Injection via Bazar Entries Search API


- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 25 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-7f6m-6c75-cf96

## What is CVE-2026-116207?

CVE-2026-116207 is a high-severity vulnerability in yeswiki, published on 25 Oct 2026. 

### Official description

YesWiki 4.6.0 before 4.7.0 and 5.0.0-alpha1 before 5.0.0-alpha4 contains an unauthenticated SQL injection vulnerability in SearchManager::prepareSearchRequest(). Field names from the query and searchfields parameters of the public Bazar entries search API are placed in a backtick-quoted alias escaped only with mysqli_real_escape_string. Attackers can supply a backtick to inject subqueries, reading data such as user password hashes or exhausting database threads with SLEEP().

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-116207?


## How do I fix CVE-2026-116207?

No fix has been published for CVE-2026-116207 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-116207 being exploited?

There is no known exploitation of CVE-2026-116207 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-116207 and fix it if it is affected.

What it is: CVE-2026-116207 is a high-severity vulnerability in yeswiki, published on 25 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116207 in the wild and no public exploit code.

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-116207/ (Markdown: https://insights.sbomify.com/CVE-2026-116207/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-116207
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-116207
- OSV: https://osv.dev/vulnerability/CVE-2026-116207

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-116207/
Summaries are generated and may contain mistakes; the official description above is the record.