# CVE-2026-104467: YesWiki before 4.6.7 Authorization Bypass via Public API Mode

> Unauthenticated attackers can bypass authorization in YesWiki to modify configuration and manage backup archives when public API mode is enabled.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/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:** 2 Oct 2026
- **Also known as:** GHSA-59xh-vh54-x5hf, GHSA-v527-6r4j-j2w2

## What is CVE-2026-104467?

CVE-2026-104467 is a critical 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 authorization bypass vulnerability in ApiService::isAuthorized() that allows unauthenticated attackers to call admin-only API routes when public API mode is enabled. Attackers can send requests to endpoints like api/ci/update_config and api/archives to overwrite configuration and list, download, or delete backup archives.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-104467 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-104467 is a critical 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-104467 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-104467/ (Markdown: https://insights.sbomify.com/CVE-2026-104467/index.md)
```

## Sources

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

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