CVE-2026-53527: perber leafwiki · Improper Privilege Management
Affects perber leafwikiSource CVE Database V5
Not known to be exploited · CVSS 8.8 High : upgrade to 0.10.1 soon.
Data as of 20 Nov 2026, 17:35 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.10.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Upgrade leafwiki and perber/leafwiki to 0.10.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| perberleafwiki | Affected
| Fixed in
|
GitHubperber/leafwikipkg:github/perber/leafwikiOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in LeafWiki version 0.10.1 and later; users should update to this version to remediate the vulnerability. If you cannot patch yet, operators should restrict account creation to trusted users only and, if possible, restrict access to the user update API to trusted users or administrators to prevent unauthorized privilege escalation.
Description
LeafWiki versions 0.1.0 through 0.10.0 contain a privilege escalation vulnerability in the user update API that allows authenticated users to escalate their privileges from regular user roles to admin. Exploitation requires a valid authenticated account. Instances without public registration and with only trusted users are at lower risk. Users should update to version 0.10.1 or later. Until patched, restricting account creation and limiting access to the user update API to trusted users or administrators is recommended.