Authenticated database read and write via unsafe LIKE
Published Sep 4, 2026 · Updated Sep 4, 2026
SQL injection in YesWiki before 4.6.6 allows remote authenticated users to read and write the database through crafted reaction paths. ReactionManager::deleteUserReaction() passes the idreaction and id path parameters into TripleStore::delete(), whose alternate branch concatenates them into an unescaped SQL LIKE clause. Any authenticated account, including a self-registered user, can reach the DELETE route and extract password hashes and email addresses or modify database records.
Summary
What happened
SQL injection in YesWiki before 4.6.6 allows remote authenticated users to read and write the database through crafted reaction paths. ReactionManager::deleteUserReaction() passes the idreaction and id path parameters into TripleStore::delete(), whose alternate branch concatenates them into an unescaped SQL LIKE clause. Any authenticated account, including a self-registered user, can reach the DELETE route and extract password hashes and email addresses or modify database records.
The record
- CVE
- CVE-2026-52775
- Published
- Sep 4, 2026
- Updated
- Sep 4, 2026
- Vendor
- YesWiki
- Product
- YesWiki
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 4, 2026CVE publishedPublication date reported by the CVE source.
- Sep 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 4.6.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Authenticated DELETE-request proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo