CVE-2026-53527: LeafWiki Vulnerable to Privilege Escalation via User Self-Service Update

Published Aug 21, 2026
·
Updated

LeafWiki is a self-hosted wiki. Versions 0.1.0 through 0.10.0 have a privilege escalation vulnerability in the user update API. An authenticated user could update their own account role and escalate privileges from a regular user, such as viewer, to admin. Exploitation requires a valid authenticated LeafWiki user account. Instances without public registration and with only trusted users are at lower practical risk. Users should update to version 0.10.1 or greater. Until a patch is available, operators should restrict account creation and ensure that only trusted users have accounts on affected LeafWiki instances. If possible, access to the user update API should be restricted to trusted users or administrators only.

Affected Software

1 affected component
LeafWiki>=0.1.0<=0.10.0, <=0.10.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade LeafWiki to a version that resolves this vulnerability.

    Fixed in 0.10.1
  2. Configuration

    Until a patch is available, restrict account creation so only trusted users have accounts on affected LeafWiki instances (instances without public registration are at lower practical risk).

    LeafWiki account creation/registration = restricted to trusted users
  3. Compensating control

    Restrict access to the user update API to trusted users or administrators only (only trusted users have accounts / no public registration reduces practical risk).

Event History

Aug 21, 2026
CVE Published
via MITRE·09:25 PM
Data Sourced
via MITRE·09:25 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are at greatest practical risk?

Affected instances that allow public registration are at greater risk because any newly registered user can authenticate and attempt to change their own role. Instances with registration disabled and only trusted accounts have lower practical risk.

2

What does an attacker need to exploit this issue?

The attacker needs a valid authenticated LeafWiki user account. No user interaction is required after authentication.

3

How can I mitigate the issue before upgrading?

Restrict account creation and ensure that only trusted users have accounts on affected instances. If possible, restrict access to the user update API to trusted users or administrators only.

4

How can I check whether an instance is affected?

LeafWiki versions 0.1.0 through 0.10.0 are affected. Upgrade to version 0.10.1 or later.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203