{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-47417 exists.","fix":"No fix has been published for CVE-2022-47417 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-47417 is a medium-severity cross-site scripting vulnerability in LogicalDOC Community Edition, published on 7 Feb 2023. 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-2022-47417 and fix it if it is affected.\n\nWhat it is: CVE-2022-47417 is a medium-severity cross-site scripting vulnerability in LogicalDOC Community Edition, published on 7 Feb 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-47417 exists.\n\nAffected product: LogicalDOC Community Edition. 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-2022-47417/ (Markdown: https://insights.sbomify.com/CVE-2022-47417/index.md)","id":"CVE-2022-47417","markdown":"https://insights.sbomify.com/CVE-2022-47417/index.md","name":"CVE-2022-47417","record":{"aliases":["GHSA-mw5v-q85w-g5pq"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"LogicalDOC DMS","requires_auth":"low_privilege","summary":"Attackers can inject malicious scripts via document file names in LogicalDOC, potentially leading to session hijacking or code execution.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"rapid7","cpe":[{"product":"logicaldoc","vendor":"logicaldoc"}],"cvss":{"score":5.4,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"LogicalDOC Enterprise and Community Edition (CE) are vulnerable to a stored (persistent, or \"Type II\") cross-site scripting (XSS) condition in the document file name.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"LogicalDOC Document File Name Stored XSS","id":"CVE-2022-47417","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"LogicalDOC Document Version Comment Stored XSS","id":"CVE-2022-47418"},"packages":[],"prev":{"headline":"LogicalDOC Chat Stored XSS","id":"CVE-2022-47416"},"products":["LogicalDOC Community Edition","LogicalDOC Enterprise"],"published":"2023-02-07","related":[{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2020-9423","kev_date_added":null,"published":"2020-03-18"},{"cvss_score":9.3,"headline":"Privilege escalation in LogicalDoc","id":"CVE-2020-13542","kev_date_added":null,"published":"2020-12-03"},{"cvss_score":8.8,"headline":"XML external entity in n/a","id":"CVE-2017-1000021","kev_date_added":null,"published":"2017-07-13"},{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2017-1000022","kev_date_added":null,"published":"2017-07-13"},{"cvss_score":8.7,"headline":"Remote Code Execution (RCE) via Arbitrary File Write In Document API","id":"CVE-2024-54449","kev_date_added":null,"published":"2025-03-14"},{"cvss_score":8.6,"headline":"Remote Code Execution (RCE) via Automation Scripting","id":"CVE-2024-54448","kev_date_added":null,"published":"2025-03-14"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2020-10366","kev_date_added":null,"published":"2020-04-07"}],"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-25","vendors":["LogicalDOC"]},"summary":"Attackers can inject malicious scripts via document file names in LogicalDOC, potentially leading to session hijacking or code execution.","url":"https://insights.sbomify.com/CVE-2022-47417/"}