{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-15236 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-15236 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-15236 is a high-severity path traversal vulnerability in Requarks wiki, published on 5 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-15236 and fix it if it is affected.\n\nWhat it is: CVE-2020-15236 is a high-severity path traversal vulnerability in Requarks wiki, published on 5 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-15236 in the wild and no public exploit code.\n\nAffected product: Requarks wiki. 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-2020-15236/ (Markdown: https://insights.sbomify.com/CVE-2020-15236/index.md)","id":"CVE-2020-15236","markdown":"https://insights.sbomify.com/CVE-2020-15236/index.md","name":"CVE-2020-15236","record":{"aliases":["GHSA-whpv-5xg2-w527"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Wiki.js","requires_auth":"none","summary":"Attackers can read arbitrary files on the server via directory traversal when local asset caching storage modules are enabled.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"wiki.js","vendor":"requarks"}],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"In Wiki.js before version 2.5.151, directory traversal outside of Wiki.js context is possible when a storage module with local asset cache fetching is enabled. A malicious user can potentially read any file on the file system by crafting a special URL that allows for directory traversal. This is only possible when a storage module implementing local asset cache (e.g Local File System or Git) is enabled and that no web application firewall solution (e.g. cloudflare) strips potentially malicious URLs. Commit 084dcd69d1591586ee4752101e675d5f0ac6dcdc fixes this vulnerability by sanitizing the path before it is passed on to the storage module. The sanitization step removes any directory traversal (e.g. `..` and `.`) sequences as well as invalid filesystem characters from the path. As a workaround, disable any storage module with local asset caching capabilities such as Local File System and Git.","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":"Directory Traversal in Wiki.js","id":"CVE-2020-15236","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Timing attack in Shrine","id":"CVE-2020-15237"},"packages":[],"prev":{"headline":"Sensitive data exposure in RACTF","id":"CVE-2020-15235"},"products":["wiki"],"published":"2020-10-05","related":[{"cvss_score":9.1,"headline":"Security feature bypass in n/a","id":"CVE-2025-56643","kev_date_added":null,"published":"2025-11-18"},{"cvss_score":8.6,"headline":"Wiki.js: Privilege Escalation via Missing Group Validation in users.update","id":"CVE-2026-44224","kev_date_added":null,"published":"2026-05-12"},{"cvss_score":8.2,"headline":"Stored XSS via SVG in Requarks/wiki","id":"CVE-2021-43855","kev_date_added":null,"published":"2021-12-27"},{"cvss_score":8.2,"headline":"Stored XSS in non-image uploads in Requarks/wiki","id":"CVE-2021-43856","kev_date_added":null,"published":"2021-12-27"},{"cvss_score":8.1,"headline":"Improper write access check in Requarks/wiki","id":"CVE-2022-23654","kev_date_added":null,"published":"2022-02-22"},{"cvss_score":7.6,"headline":"XSS in Wiki.js","id":"CVE-2021-21383","kev_date_added":null,"published":"2021-03-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["Requarks"]},"summary":"Attackers can read arbitrary files on the server via directory traversal when local asset caching storage modules are enabled.","url":"https://insights.sbomify.com/CVE-2020-15236/"}