{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-38291 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-38291 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-38291 is a medium-severity cross-site scripting vulnerability in n/a, published on 12 Sep 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-38291 and fix it if it is affected.\n\nWhat it is: CVE-2022-38291 is a medium-severity cross-site scripting vulnerability in n/a, published on 12 Sep 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-38291 in the wild and no public exploit code.\n\nAffected product: n/a. 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-38291/ (Markdown: https://insights.sbomify.com/CVE-2022-38291/index.md)","id":"CVE-2022-38291","markdown":"https://insights.sbomify.com/CVE-2022-38291/index.md","name":"CVE-2022-38291","record":{"aliases":["GHSA-3fr6-q9r2-pc9g"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"SLiMS Library System","requires_auth":"none","summary":"Attackers can execute arbitrary scripts via the Search function in SLiMS, potentially compromising user sessions.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"senayan_library_management_system","vendor":"slims"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/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":"SLiMS Senayan Library Management System v9.4.2 was discovered to contain a cross-site scripting (XSS) vulnerability via the Search function. This vulnerability allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the Search bar.","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 n/a","id":"CVE-2022-38291","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Server-side request forgery in n/a","id":"CVE-2022-38292"},"packages":[],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2022-38289"},"products":["n/a"],"published":"2022-09-12","related":[{"cvss_score":9.9,"headline":"Server-Side Request Forgery in SLiMS","id":"CVE-2023-3744","kev_date_added":null,"published":"2023-10-02"},{"cvss_score":9.8,"headline":"Server-side request forgery in n/a","id":"CVE-2022-38292","kev_date_added":null,"published":"2022-09-12"},{"cvss_score":8.8,"headline":"SQL injection in n/a","id":"CVE-2023-45996","kev_date_added":null,"published":"2023-10-31"},{"cvss_score":8.8,"headline":"SQL injection in n/a","id":"CVE-2023-40970","kev_date_added":null,"published":"2023-09-01"},{"cvss_score":8.8,"headline":"SQL injection in n/a","id":"CVE-2021-45791","kev_date_added":null,"published":"2022-03-17"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2017-12584","kev_date_added":null,"published":"2017-08-06"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2023-29850","kev_date_added":null,"published":"2023-04-14"}],"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-03","vendors":["n/a"]},"summary":"Attackers can execute arbitrary scripts via the Search function in SLiMS, potentially compromising user sessions.","url":"https://insights.sbomify.com/CVE-2022-38291/"}