YesWiki: SQL injection via the `recentchanges` action `period` argument leading to arbitrary DB read
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| YesWiki | yeswiki | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Yeswiki | Yeswiki |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-89v6-j5x6-cmj3 | YesWiki: SQL injection via the `recentchanges` action `period` argument leads to arbitrary DB read |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.379% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Yeswiki
Yeswiki yeswiki |
|
| Vendors & Products |
Yeswiki
Yeswiki yeswiki |
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | YesWiki: SQL injection via the `recentchanges` action `period` argument leading to arbitrary DB read | |
| Weaknesses | CWE-1287 CWE-89 |
|
| References |
| |
| Metrics |
cvssV3_1
|