Skip to main content
VulnerabilityPublished

CVE-2026-52775: yeswiki/yeswiki · YesWiki has Authenticated SQL Injection via ReactionManager

Affects yeswiki/yeswikiSource GCVE Database

0
Compare

Mentioned vulnerabilities

Not known to be exploited · CVSS 8.8 High : upgrade to 4.6.6 soon.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 41% 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:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Packagistyeswiki/yeswikiAffected
  • <4.6.6
Fixed in
  • 4.6.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

The suggested fix is to apply proper escaping using $this->dbService->escape() to all parameters in the vulnerable code path, matching the escaping used in the safe code path. Additionally, an audit of all TripleStore::delete() callers that pass extra SQL parameters is recommended to ensure no other injection vectors exist. If you cannot patch yet, restrict authenticated user permissions if possible and monitor for suspicious activity.

Description

YesWiki versions prior to 4.6.6 contain an authenticated SQL injection vulnerability in the ReactionManager component. Authenticated users can exploit improper input handling in the deleteUserReaction() function, where URL path parameters are concatenated directly into a SQL LIKE clause without proper escaping. This allows arbitrary SQL injection, enabling full database read and write access, including extraction of user password hashes and emails.

References

Community reviews

Loading reviews…