Security readout for executives and security teams
Plain-English summary
YesWiki versions before 4.6.6 contain a critical flaw in the Bazar import function. A crafted request may cause a logged-in user’s session to process unsafe serialized PHP data, potentially compromising the wiki and connected data. The supplied sources do not confirm public exploitation or specify the exact achievable outcome.
Executive priority
Treat this as an urgent upgrade for exposed YesWiki systems. The potential impact is severe, although exploitation requires user interaction and active exploitation is not established. Prioritize systems below 4.6.6 that are internet-facing, contain sensitive information, or are regularly accessed by privileged users.
Technical view
BazarImportAction used PHP unserialize on attacker-influenced data, creating PHP object injection risk combined with cross-site request forgery concerns (CWE-502 and CWE-352). The record describes the issue as authenticated, while its CVSS 4.0 vector states no attacker privileges and active user interaction. Version 4.6.6 contains the patch.
Likely exposure
Internet-accessible YesWiki deployments below 4.6.6 are the primary concern, especially where privileged users may interact with untrusted links or content. Exposure depends on whether BazarImportAction is reachable and exploitable in the deployment. The supplied evidence does not identify affected configurations beyond the version range.
Exploitation context
The CVSS score is 9.4 and anticipates high impact across confidentiality, integrity, and availability, including subsequent systems. User interaction is required according to the vector. The source bundle reports no KEV listing and provides no evidence of active exploitation, public proof-of-concept availability, or a confirmed gadget chain.
Researcher notes
The central issue is unsafe deserialization in BazarImportAction. CWE-352 and UI:A suggest a victim-assisted request path, but the supplied description’s “authenticated” wording conflicts with PR:N in the CVSS vector. Researchers should verify request reachability, authorization context, available PHP object chains, and actual impact without assuming code execution.
Mitigation direction
- Upgrade YesWiki to version 4.6.6 or later.
- Follow the YesWiki security advisory and release guidance during remediation.
- Restrict access to affected deployments until upgrading if immediate patching is impossible.
- Warn administrators against interacting with untrusted links while authenticated.
Validation and detection
- Inventory YesWiki instances and confirm their installed versions.
- Verify every instance runs version 4.6.6 or later.
- Confirm the vendor patch is present using the referenced commit.
- Review logs for unusual Bazar import requests or unexpected administrative changes.
- Test the upgrade in a representative environment before restoring normal exposure.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-52777 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.4 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H——GitHub_MVulnerability scoring details
Base CVSS 4.0 score
9.4CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/YesWiki/yeswiki/security/advisories/GHSA-9369-69wj-7m2fCVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/YesWiki/yeswiki/commit/8f70a8d6b8befa0e644d03c785701dbbc55b8fd0CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/YesWiki/yeswiki/releases/tag/v4.6.6CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.