# CVE-2026-104449: YesWiki before 4.6.7 Unauthenticated Page Overwrite via Bazar id_fiche

> Unauthenticated attackers can overwrite any wiki page, including protected ones, via the Bazar entry-creation flow, leading to mass defacement and content destruction.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/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-4388-phmh-jrw8, GHSA-h2q6-cgj7-p65g

## What is CVE-2026-104449?

CVE-2026-104449 is a high-severity missing authorization 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 access control vulnerability allowing unauthenticated attackers to overwrite any existing wiki page, including pages whose write ACL restricts editing, via the Bazar entry-creation flow. Attackers can submit a crafted entry with an attacker-controlled id_fiche matching an existing page, overwriting its body for mass defacement and content destruction.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-104449 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-104449 is a high-severity missing authorization 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-104449 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-104449/ (Markdown: https://insights.sbomify.com/CVE-2026-104449/index.md)
```

## Sources

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

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