Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious delete_tag GET link
-
ExploitLure admin to click link
-
ExecutionBrowser sends SameSite=Lax admin cookie
-
ImpactServer bulk-deletes tag associations
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V3 - Web Frontend Security Anti-CSRF tokens, SameSite cookies
MITRE ATT&CK
1 technique across 1 tactic: Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authenticated administrator with an active session to be lured into a top-level navigation (e.g., clicking a crafted link) to the vulnerable admintag action - this administrator interaction is the primary limiting factor. The attack depends on the delete_tag parameter being accessible via GET, which allows the SameSite=Lax session cookie to be transmitted during top-level navigation, and on the admintag action lacking CSRF token protection in YesWiki versions before 4.6.7. It does not work against default-safe states where no admin is logged in or where the admin does not interact with the attacker-controlled link; it also cannot be triggered by a cross-site background request (e.g., iframe or XHR) because SameSite=Lax blocks those, which is why top-level navigation is specifically required. Impact is limited to deletion of tag associations (tag triples), not broader data or code compromise. |
| Impact | This is a moderate-to-low real-world priority despite the medium 5.3 CVSS 4.0 score. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:P) indicates a network-reachable, low-complexity attack requiring no attacker privileges but DOES require passive user interaction - specifically a logged-in administrator being lured to a crafted link, which is the defining limiter of this CSRF (CWE-352). Impact is constrained to low integrity and low availability (VI:L/VA:L) with no confidentiality loss (VC:N/SC:N), consistent with the bounded harm of deleting tag associations rather than full compromise. No EPSS score, KEV listing, or POC was provided in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation; the absence of these signals reinforces that this is a defense-in-depth hygiene fix rather than an urgent threat. The SameSite=Lax cookie detail is important: because Lax permits top-level GET navigations to carry the session cookie, the GET-based delete_tag action remains exploitable via a simple lured link, which is why the finding is valid despite modern browser defaults. No conflicting signals were observed between the CVSS vector and the description - both agree on a remote, interaction-dependent, limited-impact CSRF. |
| Exploit ScenarioDerived | An attacker crafts a malicious page or email link pointing at the victim YesWiki instance's admintag action with a wide id range in the delete_tag parameter. When a logged-in administrator is lured into following the link via top-level navigation, their SameSite=Lax session cookie is automatically sent, and the server bulk-deletes tag triples without any CSRF token validation. No public exploit code was identified in the provided data, but the attack is trivial to construct given the GET-based design. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 02, 2026
Cross-site request forgery in the admintag action of YesWiki before 4.6.7 allows an attacker requiring no privileges (CVSS 4.0 PR:N, UI:P) to trick a logged-in administrator into clicking a crafted GET link that bulk-deletes tag associations via a wide id range in the delete_tag parameter. The attack works only because the request is issued as a top-level navigation, which lets the SameSite=Lax administrator cookie be sent; background cross-site requests such as iframes or XHR are blocked by SameSite=Lax, and the admin must have an active session and interact with the link. Impact is confined to integrity and availability of tag triples (C:N/I:L/A:L) rather than broader data or code compromise, and no public exploit code has been identified at time of analysis.
RemediationAI
Vendor-released patch: upgrade to YesWiki 4.6.7, which is the first release at or above the fixed boundary ("before 4.6.7" per the advisory at https://github.com/YesWiki/yeswiki/security/advisories/GHSA-5c27-6gcm-hc7x); administrators should also review tag triples for deletions that cannot be attributed to legitimate editing and restore from backup if tampering is suspected. Until the upgrade can be applied, the primary compensating control is to prevent the forged top-level navigation from carrying the admin cookie: instruct administrators to log out of YesWiki when browsing untrusted links or to use a dedicated browser profile/session for wiki administration, keeping in mind this only works when the session is not active. Because exploitation depends on the SameSite=Lax cookie surviving a top-level GET, raising the session cookie to SameSite=Strict (or shortening admin session lifetimes) breaks the attack path, but the trade-off is that legitimate inbound links to authenticated pages will no longer carry the session and users may be logged out more frequently. Blocking or throttling unauthenticated GET requests to the admintag action at a reverse proxy or WAF, and requiring admins to reach the wiki over a trusted network/VPN, further reduces exposure but can interfere with legitimate administrative workflows that rely on link-based navigation. No public exploit code has been identified at time of analysis, so these measures should be prioritized by exposure of the administrative interface rather than urgency of confirmed attacks.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is CWE-352 (Cross-Site Request Forgery) in YesWiki, a PHP-based wiki/CMS. The admintag action performs a state-changing tag-deletion operation but accepts the delete_tag parameter over GET and lacks CSRF token validation, so any request reaching that endpoint with a valid admin session is honored. Tag associations in YesWiki are stored as triples (subject-predicate-object semantic links), so deleting them silently corrupts the wiki's tagging/ontology layer. The exploit chain depends on two browser-behavior details: the admin's session cookie is configured SameSite=Lax, which permits it on top-level GET navigations but not on cross-site subresource requests, and the delete_tag parameter tolerates a wide id range, enabling bulk deletion in a single click. The CPE cpe:2.3:a:yeswiki:yeswiki:*:*:*:*:*:*:*:* with EUVD's range "yeswiki 0 <4.6.7" confirms every release up to 4.6.7 is affected; the CVSS 4.0 vector rates UI:P (passive interaction) while the independently assessed CVSS 3.1 vector rates UI:R, both reflecting that the victim administrator must be induced to visit an attacker-supplied link.
Know when Yeswiki gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N
Remote low-complexity CSRF needing no attacker auth (PR:N) but requiring admin interaction (UI:R); no confidentiality impact, limited integrity/availability from tag deletion.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
1DescriptionCVE.org
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.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Request Forgery exploits the automatic credential inclusion behavior of web browsers.
YesWiki is a wiki system written in PHP. Rated high severity (CVSS 8.6), this vulnerability is remotely exploitable, no
YesWiki is a wiki system written in PHP. Rated critical severity (CVSS 10.0), this vulnerability is remotely exploitable
Remote code execution in YesWiki prior to 4.6.6 allows unauthenticated attackers to inject arbitrary PHP via the Bazar C
YesWiki is a wiki system written in PHP. Rated critical severity (CVSS 9.1), this vulnerability is remotely exploitable,
YesWiki is a wiki system written in PHP. Rated high severity (CVSS 7.6), this vulnerability is remotely exploitable, no
Unauthenticated server-side request forgery in YesWiki before 4.7.0 lets any remote visitor make the wiki server issue H
YesWiki is a wiki system written in PHP. Rated medium severity (CVSS 5.8), this vulnerability is remotely exploitable, n
YesWiki is a wiki system written in PHP. Rated medium severity (CVSS 6.3), this vulnerability is remotely exploitable, n
Cross Site Scripting vulnerability in YesWiki v.4.54 allows a remote attacker to execute arbitrary code via a crafted pa
YesWiki version <= cercopitheque beta 1 contains a PHP Object Injection vulnerability in Unserialising user entered para
Authorization bypass in YesWiki before 4.6.7 lets unauthenticated remote attackers call admin-only API routes when the i
Unauthenticated attackers can delete or overwrite federated entries in YesWiki instances before 4.6.7 that have Activity
EUVD-2026-91464
GHSA-x3mc-2q4x-cvvm
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB