Quick answers
- Is CVE-2026-52775 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-52775 being exploited in the wild.
- How severe is CVE-2026-52775?
- High severity, with a CVSS score of 8.8, published 5 September 2026.
- Which products and versions are affected?
- yeswiki/yeswiki (Packagist) < 4.6.6, ECOSYSTEM:introduced=0,fixed=4.6.6; YesWiki < 4.6.6.
- Is there a fix for CVE-2026-52775?
- Yes. yeswiki/yeswiki (Packagist): upgrade to 4.6.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-52775 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-52775?
- Check whether you run yeswiki/yeswiki (Packagist) or YesWiki at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- yeswiki/yeswiki (Packagist): upgrade to 4.6.6 or later
composer require yeswiki/yeswiki:^4.6.6
Technical details
An authenticated SQL injection vulnerability exists in YesWiki's `ReactionManager::deleteUserReaction()` function. The root cause is the direct concatenation of the `{idreaction}` and `{id}` URL path parameters into a SQL LIKE clause within the `TripleStore::delete()` method without proper escaping or parameterization. While one code path in the component correctly uses `$this->dbService->escape()`, an alternative branch fails to do so. An attacker with any level of authenticated access can exploit this via a DELETE request to the `/api/reactions/` endpoint to perform time-based blind SQL injection, enabling full database read/write access. The issue is patched in version 4.6.6.
Affected products
- YesWiki YesWiki < 4.6.6
Identifiers
- CVE-2026-52775
- GHSA-4pf7-cc4r-g63h
Timeline
- 2026-06-02: disclosed: Initial disclosure and commit fix
- 2026-07-09: advisory: GitHub Advisory published