{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-53529 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-53529 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-53529 is a medium-severity cross-site scripting vulnerability in perber leafwiki, published on 21 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-53529 and fix it if it is affected.\n\nWhat it is: CVE-2026-53529 is a medium-severity cross-site scripting vulnerability in perber leafwiki, published on 21 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-53529 in the wild and no public exploit code.\n\nAffected product: perber leafwiki. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-53529/ (Markdown: https://insights.sbomify.com/CVE-2026-53529/index.md)","id":"CVE-2026-53529","markdown":"https://insights.sbomify.com/CVE-2026-53529/index.md","name":"CVE-2026-53529","record":{"aliases":["GHSA-j344-qxqm-wg64"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"LeafWiki self-hosted wiki","requires_auth":"low_privilege","summary":"Attackers with editor permissions can inject scripts into page titles, executing code in victims' browsers via search results.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"LeafWiki vulnerable to stored XSS via search-result title (highlight() returns raw title into dangerouslySetInnerHTML)","id":"CVE-2026-53529","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"ratex-parser panics on `\\verb` with a multibyte delimiter (UTF-8 byte-boundary slice)","id":"CVE-2026-53530"},"packages":[],"prev":{"headline":"FileWiki has path traversal in RenameAsset via unsanitized oldFilename parameter","id":"CVE-2026-53528"},"products":["leafwiki"],"published":"2026-08-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-21","vendors":["perber"]},"summary":"Attackers with editor permissions can inject scripts into page titles, executing code in victims' browsers via search results.","url":"https://insights.sbomify.com/CVE-2026-53529/"}