/

CVE-2026-53528

Severity:

HIGH RISK

(8.8)

Path Traversal (CWE-23) in LeafWiki Asset Rename Function

CVE-2026-53528

Deferred

Vulnerability type

Category:

Path Traversal

CWE:

CWE-23

Impact:

Sensitive Local File Disclosure

Severity:

HIGH RISK

(8.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

LeafWiki contains a path traversal vulnerability in its asset rename functionality that can let an authenticated editor move server-accessible files into a page's asset directory. Those files may then become downloadable as page assets, potentially exposing sensitive application data when the server process can read it.

Affected context

The vulnerability occurs in self-hosted LeafWiki deployments where the asset rename feature accepts paths that are not sufficiently confined to the intended asset location. Risk depends on the LeafWiki process being able to read sensitive files and on an authenticated account having editor permissions.

Exploit preconditions

  • Attack surface: LeafWiki's authenticated asset rename functionality
  • Required access: An authenticated account with editor permissions
  • Trigger point: Processing a file move or rename into a page's asset directory
  • Why exploitation is possible: Path handling may allow references outside the intended asset directory, while the server process can access and subsequently serve the moved file

Why this happens

The underlying issue is insufficient path validation during file rename or move operations. User-controlled path components are not reliably constrained to the permitted asset directory, allowing traversal outside the expected filesystem boundary. This maps to CWE-23: Path Traversal, where crafted path references can cause an application to access or manipulate unintended files.

Potential impact

  • Sensitive local files could be copied or moved into downloadable page assets
  • Application databases, configuration files, or other readable data may be disclosed
  • Confidentiality of wiki content and deployment information could be reduced
  • File organization or application behavior could be altered through unauthorized moves

General mitigation guidance

Mitigation generally focuses on enforcing a strict filesystem boundary for asset operations and reducing the trust placed in user-supplied paths.

Common defensive patterns include:

  • Resolve paths canonically and verify that the result remains within the designated asset directory
  • Prefer server-generated asset identifiers over user-controlled filesystem paths
  • Reject traversal components, symbolic-link escapes, and cross-directory rename targets
  • Run LeafWiki with the least filesystem privileges necessary
  • Restrict process access to sensitive files outside required application directories
  • Limit editor permissions to trusted users until a security fix is deployed
  • Apply the vendor-supported security update through the normal maintenance process

How teams detect issues like this

Organizations can look for path traversal risks through:

  • Static analysis rules identifying filesystem operations that combine user input with paths
  • Code review checks for missing canonicalization and containment validation
  • Tests covering traversal sequences, absolute paths, symbolic links, and alternate path representations
  • Runtime monitoring for asset operations involving unexpected directories or sensitive file locations
  • Authorization and policy checks that restrict asset-management capabilities to trusted roles

Automated security review tools may help identify unsafe path construction and missing boundary checks.

Sources

SourceLink
github.comgithub.com/perber/leafwiki/security/advisories/GHSA-g2wp-jm5c-jqfj

Frequently asked

questions

Exploitation generally requires an authenticated LeafWiki account with editor permissions, along with a deployment where the server process can read the targeted files.

No. Exposure depends on the files accessible to the LeafWiki process and on whether the asset handling path allows those files to be placed in a downloadable asset location.

Constrain every rename source and destination to approved directories after canonical path resolution, and ensure that file operations cannot escape the intended asset boundary.

Combine strict path containment checks with least-privilege filesystem permissions, trusted-role controls, symbolic-link defenses, and automated tests for path traversal cases.

Find out what's already
exploitable in your codebase.