CVE-2026-52763
Received Received - Intake

SQL Injection in YesWiki Prior to 4.6.6

Publication date: 2026-09-05

Last updated on: 2026-09-05

Assigner: GitHub, Inc.

Description
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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-05
Last Modified
2026-09-05
Generated
2026-09-05
AI Q&A
2026-09-05
EPSS Evaluated
N/A
NVD
CVE-2026-52763

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
yeswiki yeswiki 4.6.6

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-1287 The product receives input that is expected to be of a certain type, but it does not validate or incorrectly validates that the input is actually of the expected type.
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. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a stored SQL injection in YesWiki versions before 4.6.6. It occurs in the recentchanges action where a period argument is accepted from two sources. One source is validated, but the other bypasses validation and flows into a database query without proper escaping. This allows attackers to inject malicious SQL code that reads database contents.

Detection Guidance

Check if your YesWiki instance is running a version prior to 4.6.6. Inspect the recentchanges action for suspicious SQL queries or unexpected data exposure in responses. Look for UNION-based injection patterns in logs or database queries.

Impact Analysis

The vulnerability allows any user who can edit a page to read the entire YesWiki database. On default installations, this includes anonymous users. Once a malicious page is saved, every visitor to that page will see the exfiltrated data. The impact is arbitrary database read access.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating GDPR and HIPAA requirements for data protection and confidentiality. It may result in data breaches, non-compliance penalties, and loss of trust due to unauthorized data exposure.

Mitigation Strategies

Upgrade YesWiki to version 4.6.6 or later immediately. If upgrading is not possible, restrict write access to trusted users by changing default_write_acl from '*' to specific user groups. Review and sanitize all user inputs in the recentchanges action.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-52763. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart