# CVE-2026-104457: YesWiki before 4.6.7 SQL Injection via filtertags filterN parameter

> Unauthenticated attackers can inject SQL via the filtertags parameter to read arbitrary database data, including password hashes, in YesWiki.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-f8w7-2q27-5p28, GHSA-p87r-f4x4-8r4g

## What is CVE-2026-104457?

CVE-2026-104457 is a high-severity SQL injection vulnerability in yeswiki, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

YesWiki before 4.6.7 contains an SQL injection vulnerability in the Bazar filtertags action, which wraps unescaped filterN attribute tokens in quotes and concatenates them into a raw tags.value IN (...) clause. Unauthenticated attackers on default installs can save filtertags markup in a page with a trailing-backslash token that breaks quote parity under MySQL backslash escaping. This lets them inject a five-column UNION subquery to read arbitrary table data such as password hashes.

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

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


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

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

## Is CVE-2026-104457 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-104457 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-104457 is a high-severity SQL injection vulnerability in yeswiki, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-104457 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-104457/ (Markdown: https://insights.sbomify.com/CVE-2026-104457/index.md)
```

## Sources

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

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