{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-5619 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-5619 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-5619 is a medium-severity cross-site scripting vulnerability in Kajitori Co.,Ltd Exment, published on 25 Aug 2020. 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-2020-5619 and fix it if it is affected.\n\nWhat it is: CVE-2020-5619 is a medium-severity cross-site scripting vulnerability in Kajitori Co.,Ltd Exment, published on 25 Aug 2020. 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-2020-5619 in the wild and no public exploit code.\n\nAffected product: Kajitori Co.,Ltd Exment. 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-5619/ (Markdown: https://insights.sbomify.com/CVE-2020-5619/index.md)","id":"CVE-2020-5619","markdown":"https://insights.sbomify.com/CVE-2020-5619/index.md","name":"CVE-2020-5619","record":{"aliases":["GHSA-337r-3rxv-c739"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Exment web application","requires_auth":"low_privilege","summary":"Remote authenticated attackers can inject arbitrary scripts or HTML into Exment, potentially leading to session hijacking or malicious actions.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jpcert","cpe":[{"product":"exment","vendor":"exceedone"}],"cvss":{"score":5.4,"severity":"medium","source":"nvd","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":"Cross-site scripting vulnerability in Exment prior to v3.6.0 allows remote authenticated attackers to inject arbitrary script or HTML via unspecified vectors.","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":"Cross-site scripting in Exment","id":"CVE-2020-5619","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in Exment","id":"CVE-2020-5620"},"packages":[],"prev":{"headline":"Privilege escalation in SKYSEA Client View","id":"CVE-2020-5617"},"products":["Exment"],"published":"2020-08-25","related":[{"cvss_score":8.8,"headline":"exceedone/exment and exceedone/laravel-admin SQL Injection vulnerability","id":"CVE-2022-37333","kev_date_added":null,"published":"2022-08-24"},{"cvss_score":5.4,"headline":"Cross-site scripting in Exment","id":"CVE-2024-47793","kev_date_added":null,"published":"2024-10-18"},{"cvss_score":5.4,"headline":"exceedone/exment and exceedone/laravel-admin Cross-site Scripting vulnerability","id":"CVE-2022-38080","kev_date_added":null,"published":"2022-08-24"},{"cvss_score":5.4,"headline":"Cross-site scripting in Exment","id":"CVE-2022-38089","kev_date_added":null,"published":"2022-08-24"},{"cvss_score":5.4,"headline":"Cross-site scripting in Exment","id":"CVE-2020-5620","kev_date_added":null,"published":"2020-08-25"},{"cvss_score":3.8,"headline":"Missing authorization in Exment","id":"CVE-2024-46897","kev_date_added":null,"published":"2024-10-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":["Kajitori Co.,Ltd"]},"summary":"Remote authenticated attackers can inject arbitrary scripts or HTML into Exment, potentially leading to session hijacking or malicious actions.","url":"https://insights.sbomify.com/CVE-2020-5619/"}