{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-27409 exists.","fix":"No fix has been published for CVE-2025-27409 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-27409 is a high-severity path traversal vulnerability in laurent22 joplin, published on 30 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-27409 and fix it if it is affected.\n\nWhat it is: CVE-2025-27409 is a high-severity path traversal vulnerability in laurent22 joplin, published on 30 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-27409 exists.\n\nAffected product: laurent22 joplin. 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-2025-27409/ (Markdown: https://insights.sbomify.com/CVE-2025-27409/index.md)","id":"CVE-2025-27409","markdown":"https://insights.sbomify.com/CVE-2025-27409/index.md","name":"CVE-2025-27409","record":{"aliases":["GHSA-5xv6-7jm3-fmg5"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Joplin Server","requires_auth":"none","summary":"Attackers can read arbitrary files outside intended directories in Joplin Server due to insufficient path validation in plugin asset handling.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"joplin","vendor":"joplin_project"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Joplin is a free, open source note taking and to-do application, which can handle a large number of notes organised into notebooks. Prior to version 3.3.3, path traversal is possible in Joplin Server if static file path starts with `css/pluginAssets` or `js/pluginAssets`. The `findLocalFile` function in the `default route` calls `localFileFromUrl` to check for special `pluginAssets` paths. If the function returns a path, the result is returned directly, without checking for path traversal. The vulnerability allows attackers to read files outside the intended directories. This issue has been patched in version 3.3.3.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Joplin Server Vulnerable to Path Traversal","id":"CVE-2025-27409","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"PwnDoc Arbitrary File Write to RCE using Path Traversal in backup restore as admin","id":"CVE-2025-27410"},"packages":[],"prev":{"headline":"Manifest Uses a One-Way Hash without a Salt","id":"CVE-2025-27408"},"products":["joplin"],"published":"2025-04-30","related":[{"cvss_score":9.8,"headline":"Joplin Vulnerable to Code Injection","id":"CVE-2022-23340","kev_date_added":null,"published":"2022-02-08"},{"cvss_score":9.7,"headline":"Joplin has a parsing error leading to Cross-site Scripting (XSS)","id":"CVE-2024-40643","kev_date_added":null,"published":"2024-09-09"},{"cvss_score":8.9,"headline":"Arbitrary code execution on click of PDF links in Joplin","id":"CVE-2023-45673","kev_date_added":null,"published":"2024-06-21"},{"cvss_score":8.8,"headline":"Privilege escalation in Joplin server via user patch endpoint","id":"CVE-2025-27134","kev_date_added":null,"published":"2025-04-30"},{"cvss_score":8.2,"headline":"Safe mode Cross-site Scripting (XSS) vulnerability in Joplin","id":"CVE-2023-37898","kev_date_added":null,"published":"2024-06-21"},{"cvss_score":8.2,"headline":"Cross-site Scripting (XSS) when pasting HTML into the rich text editor in Joplin","id":"CVE-2023-38506","kev_date_added":null,"published":"2024-06-21"},{"cvss_score":8.2,"headline":"Cross site scripting (XSS) when clicking on an untrusted `\u003cmap\u003e` link in Joplin","id":"CVE-2023-39517","kev_date_added":null,"published":"2024-06-21"}],"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-30","vendors":["laurent22"]},"summary":"Attackers can read arbitrary files outside intended directories in Joplin Server due to insufficient path validation in plugin asset handling.","url":"https://insights.sbomify.com/CVE-2025-27409/"}