CVE-2026-104453 YesWiki before 4.6.7 CSRF Tag Deletion via admintag Action
Medium 5.3
Published
Updated
Check this codebase for CVE-2026-104453 and fix it if it is affected.
What it is: CVE-2026-104453 is a medium-severity vulnerability in yeswiki, published on 2 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-104453 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-104453/ (Markdown: https://insights.sbomify.com/CVE-2026-104453/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-104453?
CVE-2026-104453 is a medium-severity vulnerability in yeswiki, published on 2 Oct 2026.
Official description
YesWiki before 4.6.7 contains a cross-site request forgery vulnerability in the admintag action that allows attackers to delete tag associations by luring administrators to crafted GET links. Attackers can supply a wide id range in the delete_tag parameter via top-level navigation, carrying the SameSite=Lax admin cookie, to bulk-delete tag triples.
Weakness: CWE-352
Which versions are affected by CVE-2026-104453?
How do I fix CVE-2026-104453?
No fix has been published for CVE-2026-104453 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-104453 being exploited?
There is no known exploitation of CVE-2026-104453 in the wild and no public exploit code.
Sources
Also known as GHSA-5c27-6gcm-hc7x, GHSA-x3mc-2q4x-cvvm.