Skip to main content
VulnerabilityPublished

CVE-2026-53529: perber leafwiki · Cross-site Scripting

Affects perber leafwikiSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.8 Medium : upgrade to 0.10.2 when convenient.

Data as of 20 Nov 2026, 17:35 UTC

CVSS 4.0 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.10.2
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 perber leafwiki to 0.10.2.

Affected software

ProductAffectedFixed in
perberleafwikiAffected
  • <0.10.2
Fixed in
  • 0.10.2

AI-suggested

A fix is available in LeafWiki version 0.10.2, which sanitizes page titles in search results to prevent them from being interpreted as raw HTML. Users should upgrade to version 0.10.2 or later to remediate this vulnerability. No other specific mitigations are indicated. Patch status is confirmed by the vendor advisory stating the issue is fixed in 0.10.2.

Description

LeafWiki is a self-hosted wiki. Prior to version 0.10.2, page titles returned by the search API could be rendered as raw HTML in the frontend. A user with editor or administrator permissions could create or modify a page title containing an HTML/JavaScript payload. When another user searched for a matching term, the payload could execute in the victim’s browser. The impact depends on deployment configuration. With `--public-access` enabled, unauthenticated visitors could be affected. In authenticated-only deployments, the issue could be used for cross-user XSS against logged-in users who can access search results. The issue has been fixed in version 0.10.2 by ensuring that author-controlled page titles in search results are not interpreted as raw HTML by the browser while preserving search result highlighting.

References

Community reviews

Loading reviews…