# CVE-2026-104451: YesWiki before 4.6.7 CSRF Page Revision Restore via RevisionsHandler

> Attackers can trick authenticated users into restoring old page revisions, overwriting current content with stale or vandalized data.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Oct 2026
- **Updated:** 2 Oct 2026
- **Also known as:** GHSA-q9vm-p57f-8mmp, GHSA-vj5g-974q-7ff3

## What is CVE-2026-104451?

CVE-2026-104451 is a medium-severity vulnerability in yeswiki, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

YesWiki before 4.6.7 contains a cross-site request forgery vulnerability in RevisionsHandler that allows attackers to restore old page revisions through GET requests lacking CSRF token validation. Attackers can lure write-capable users into a top-level navigation with the restoreRevisionId parameter, silently overwriting current page content with stale or vandalized revisions.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-104451 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-104451 is a medium-severity vulnerability in yeswiki, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-104451 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-104451/ (Markdown: https://insights.sbomify.com/CVE-2026-104451/index.md)
```

## Sources

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

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