CVE-2026-53528: FileWiki has path traversal in RenameAsset via unsanitized oldFilename parameter
LeafWiki is a self-hosted wiki. Versions 0.3.0 through 0.10.0 have a path traversal vulnerability in LeafWiki’s asset rename functionality. An authenticated user with editor permissions could move files that are accessible to the LeafWiki server process into a page’s asset directory. This could allow sensitive local files, such as the application database, to become downloadable as page assets. Users should update to version 0.10.1 or greater. As an additional mitigation, operators should ensure that the LeafWiki process runs with the least privileges necessary and does not have filesystem access to sensitive files outside the application’s required directories. Until a patch is applied, operators may reduce risk by restricting editor access to trusted users only and by limiting the filesystem permissions of the LeafWiki process.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
LeafWikito a version that resolves this vulnerability.Fixed in 0.10.1 - Configuration
Until a patch is applied, restrict editor permissions to trusted users only (avoid granting editor permissions broadly).
LeafWiki editor access permissions = restrict to trusted users only - Compensating control
Until a patch is applied, run the LeafWiki process with the least privileges necessary and remove filesystem access to sensitive files outside the application’s required directories (limit LeafWiki process filesystem permissions to only required asset/application directories).
Event History
Frequently Asked Questions
Which users can exploit this issue?
An authenticated user with editor permissions can exploit it. Restrict editor access to trusted users until the instance is updated.
What files are at risk of exposure?
Files accessible to the LeafWiki server process may be moved into a page asset directory and made downloadable. This can include sensitive local files such as the application database if the process can read them.
Are all affected versions vulnerable by default?
Versions 0.3.0 through 0.10.0 are affected. Exposure depends on whether an editor account exists and what files the LeafWiki process can access.
What mitigation is available before upgrading?
Run the LeafWiki process with only the filesystem permissions it needs, preventing access to sensitive files outside required application directories. Also restrict editor permissions to trusted users.
How can this be remediated?
Update LeafWiki to version 0.10.1 or later.