Page access bypass via boundaryless path matching
Published Sep 16, 2026 · Updated Sep 18, 2026
Incorrect authorization in Requarks.io Wiki.js 2.5.314 and earlier allows remote authenticated users to read and modify unrelated pages. The checkAccess function in server/core/auth.js applies START and END rules with bare string prefix and suffix comparisons, without requiring a path-separator boundary. A user needs only folder-scoped page permissions; a colliding page path then exposes content and permits changes allowed by that rule.
Summary
What happened
Incorrect authorization in Requarks.io Wiki.js 2.5.314 and earlier allows remote authenticated users to read and modify unrelated pages. The checkAccess function in server/core/auth.js applies START and END rules with bare string prefix and suffix comparisons, without requiring a path-separator boundary. A user needs only folder-scoped page permissions; a colliding page path then exposes content and permits changes allowed by that rule.
The record
- CVE
- CVE-2026-92776
- Published
- Sep 16, 2026
- Updated
- Sep 18, 2026
- Vendor
- Requarks.io
- Product
- Wiki.js
- Classifications
- CWE-863, T1213, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 16, 2026CVE publishedPublication date reported by the CVE source.
- Sep 18, 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=0 <=2.5.314
What conditions does exploitation require?
What is affected?
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.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
- Finding 3 page-rule prefix-collision 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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started