CVE-2026-52773: yeswiki/yeswiki · YesWiki Vulnerable to Reflected XSS via Unescaped Archived-Revision `time` Parameter in `handlers/page/show.php`
Affects yeswiki/yeswikiSource GCVE Database
Not known to be exploited · public detection template (Nuclei) · CVSS 6.1 Medium : upgrade to 4.6.6 when convenient.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.6.6
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 9 Jul 2026
Detectable: evidence found.
nuclei template: YesWiki Archived Revision - Cross-Site Scripting
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade yeswiki/yeswiki to 4.6.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Packagistyeswiki/yeswiki | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, restrict write access to trusted users only and avoid configurations that allow anonymous editing of public pages. Review and sanitize user input in the 'time' parameter before rendering it in HTML contexts, ideally applying proper escaping such as htmlspecialchars() to prevent XSS.
Description
YesWiki versions from 4.1.0 up to but not including 4.6.6 are vulnerable to a reflected cross-site scripting (XSS) issue via the unescaped 'time' GET parameter in the archived revision view handler (handlers/page/show.php). The vulnerability occurs because the 'time' parameter is reflected into a hidden HTML input field without proper escaping, allowing an attacker to inject arbitrary JavaScript. Exploitation requires the victim to have both read and write access to the target page, although some default configurations may allow anonymous exploitation on public editable pages. The issue arises due to MySQL's coercion of malformed DATETIME strings, enabling the crafted payload to match an archived revision and be reflected unescaped in the response.