YesWiki before 4.6.7 contains a second-order SQL injection vulnerability in AclService::updateRequestWithACL, where a stored username is… (CVE-2026-104456)
YesWiki versions prior to 4.6.7 contain a second-order SQL injection vulnerability in the AclService::updateRequestWithACL function. This vulnerability arises because a stored username is concatenated without proper escaping into a read-ACL LIKE clause. An attacker can exploit this by self-registering an account with a specially crafted username containing a double-quote payload, enabling them to bypass read ACLs and access restricted database contents.
AI Analysis
Technical Summary
The vulnerability in YesWiki before version 4.6.7 is a second-order SQL injection located in the AclService::updateRequestWithACL method. The flaw occurs due to unescaped concatenation of a stored username into a SQL read-ACL LIKE clause. Attackers can register an account with a malicious username payload containing a double-quote character, which is then used in subsequent ACL-filtered queries to bypass access controls and read sensitive database information. This vulnerability is tracked as CVE-2026-104456 and has a CVSS v3.1 score of 7.6, indicating high severity.
Potential Impact
Successful exploitation allows an attacker with low privileges (self-registered user) to bypass read access control lists and read sensitive database contents that should be restricted. This leads to confidentiality breaches and partial integrity and availability impacts as indicated by the CVSS vector (C:H/I:L/A:L).
Mitigation Recommendations
A fix is available in YesWiki version 4.6.7 and later. Users should upgrade to version 4.6.7 or newer to remediate this vulnerability. No other mitigation or temporary workaround is indicated in the provided data.
YesWiki before 4.6.7 contains a second-order SQL injection vulnerability in AclService::updateRequestWithACL, where a stored username is… (CVE-2026-104456)
Description
YesWiki versions prior to 4.6.7 contain a second-order SQL injection vulnerability in the AclService::updateRequestWithACL function. This vulnerability arises because a stored username is concatenated without proper escaping into a read-ACL LIKE clause. An attacker can exploit this by self-registering an account with a specially crafted username containing a double-quote payload, enabling them to bypass read ACLs and access restricted database contents.
CVSS v3.1
Score 7.6high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in YesWiki before version 4.6.7 is a second-order SQL injection located in the AclService::updateRequestWithACL method. The flaw occurs due to unescaped concatenation of a stored username into a SQL read-ACL LIKE clause. Attackers can register an account with a malicious username payload containing a double-quote character, which is then used in subsequent ACL-filtered queries to bypass access controls and read sensitive database information. This vulnerability is tracked as CVE-2026-104456 and has a CVSS v3.1 score of 7.6, indicating high severity.
Potential Impact
Successful exploitation allows an attacker with low privileges (self-registered user) to bypass read access control lists and read sensitive database contents that should be restricted. This leads to confidentiality breaches and partial integrity and availability impacts as indicated by the CVSS vector (C:H/I:L/A:L).
Mitigation Recommendations
A fix is available in YesWiki version 4.6.7 and later. Users should upgrade to version 4.6.7 or newer to remediate this vulnerability. No other mitigation or temporary workaround is indicated in the provided data.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-m352-5gh7-99x6
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-104456"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6abfee8ea43b0b3b89e55035
Added to database: 10/02/2026, 17:49:02 UTC
Last enriched: 10/02/2026, 17:58:36 UTC
Last updated: 10/02/2026, 21:26:11 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.