Skip to main content

YesWiki before 4.6.7 contains an access control vulnerability allowing unauthenticated attackers to overwrite any existing wiki page, including… (CVE-2026-104449)

0
High
Published: 10/02/2026 (10/02/2026, 12:31:16 UTC)
Source: GCVE Database

Description

YesWiki versions prior to 4.6.7 have an access control vulnerability that allows unauthenticated attackers to overwrite any existing wiki page, including those with restricted write access controls. This occurs via the Bazar entry-creation flow by submitting a crafted entry with an attacker-controlled id_fiche matching an existing page, enabling mass defacement or content destruction.

CVSS v3.1

Score 6.5medium

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:L

Affected software

GitHub Actionsmore threats →ai
yeswiki/yeswiki
pkg:github/yeswiki/yeswiki
Affected versions
<4.6.7

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/02/2026, 17:58:42 UTC

Technical Analysis

CVE-2026-104449 describes an access control vulnerability in YesWiki before version 4.6.7. The flaw allows unauthenticated attackers to overwrite existing wiki pages regardless of their write ACL restrictions by exploiting the Bazar entry-creation mechanism. Attackers can craft entries with an id_fiche that matches an existing page, overwriting its content. This vulnerability can lead to mass defacement and destruction of wiki content.

Potential Impact

The vulnerability allows unauthenticated attackers to modify the content of any existing wiki page, bypassing access control restrictions. This can result in mass defacement and destruction of wiki content, impacting the integrity and availability of the wiki.

Mitigation Recommendations

A fix is available in YesWiki version 4.6.7. Users should upgrade to version 4.6.7 or later to remediate this vulnerability. No other mitigation guidance is provided in the available data.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
GHSA-h2q6-cgj7-p65g
Osv Schema Version
1.4.0
Aliases
["CVE-2026-104449"]
Database Specific Severity
HIGH
Cvss Version
3.1

Threat ID: 6abfee8ea43b0b3b89e55037

Added to database: 10/02/2026, 17:49:02 UTC

Last enriched: 10/02/2026, 17:58:42 UTC

Last updated: 10/02/2026, 21:26:08 UTC

Views: 2

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses