YesWiki up to 4.6.5 recentchanges recentchanges.php getRecentlyChanged period sql injection

Summaryinfo

A vulnerability was found in YesWiki up to 4.6.5. It has been rated as critical. This affects the function PageManager::getRecentlyChanged of the file actions/recentchanges.php of the component recentchanges. The manipulation of the argument period leads to sql injection. This vulnerability is listed as CVE-2026-52763. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability was found in YesWiki up to 4.6.5. It has been rated as critical. This issue affects the function PageManager::getRecentlyChanged of the file actions/recentchanges.php of the component recentchanges. The manipulation of the argument period with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

YesWiki is a wiki system written in PHP. Prior to version 4.6.6, the recentchanges action (actions/recentchanges.php) accepts a period argument from two disjoint parameter spaces. A whitelist validates only the URL form against ['day','week','month']. The action-argument form takes the else branch with no validation, and the value flows into PageManager::getRecentlyChanged(), where it is interpolated into a WHERE time >= '...' ORDER BY time DESC clause without escaping or parameterization. UNION-based injection succeeds, the leaked rows render into the response page, so any visitor of the trigger page sees the exfiltrated data. The vulnerability provides arbitrary read of the YesWiki database to anyone who can save the trigger page. On a default install (default_write_acl='*'), this includes anonymous users, subject to the hashcash JS check on the page-edit form. Once the trigger page is saved, every subsequent view fires the injection as the SQLi is stored. Stored SQL injection is reachable through the page-edit flow, with arbitrary database read. This issue has been patched in version 4.6.6.

It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-52763 since 06/08/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.

By approaching the search of inurl:actions/recentchanges.php it is possible to find vulnerable targets with Google Hacking.

Upgrading to version 4.6.6 eliminates this vulnerability.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• Content Management System

Name

• YesWiki

Version

• 4.6.0
• 4.6.1
• 4.6.2
• 4.6.3
• 4.6.4
• 4.6.5

Website

• Product: https://github.com/YesWiki/yeswiki/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion