{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-32715 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-32715 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-32715 is a medium-severity cross-site scripting vulnerability in Splunk App for Lookup File Editing, published on 1 Jun 2023. 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-2023-32715 and fix it if it is affected.\n\nWhat it is: CVE-2023-32715 is a medium-severity cross-site scripting vulnerability in Splunk App for Lookup File Editing, published on 1 Jun 2023. 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-2023-32715 in the wild and no public exploit code.\n\nAffected product: Splunk App for Lookup File Editing. 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-2023-32715/ (Markdown: https://insights.sbomify.com/CVE-2023-32715/index.md)","id":"CVE-2023-32715","markdown":"https://insights.sbomify.com/CVE-2023-32715/index.md","name":"CVE-2023-32715","record":{"aliases":["GHSA-49f3-f85j-5g57"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Splunk app","requires_auth":"none","summary":"Attackers can execute malicious JavaScript on a victim's machine via self-XSS in the Splunk App for Lookup File Editing, requiring user interaction.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Splunk","cpe":[{"product":"splunk_app_for_lookup_file_editing","vendor":"splunk"}],"cvss":{"score":4.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/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":"In the Splunk App for Lookup File Editing versions below 4.0.1, a user can insert potentially malicious JavaScript code into the app, which causes that code to run on the user’s machine. The app itself does not contain the potentially malicious JavaScript code. The vulnerability requires the attacker to phish the victim by tricking them into initiating a request within their browser, and requires additional user interaction to trigger. The attacker cannot exploit the vulnerability at will.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Self Cross-Site Scripting (XSS) on Splunk App for Lookup File Editing","id":"CVE-2023-32715","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of Service via the 'dump' SPL command","id":"CVE-2023-32716"},"packages":[],"prev":{"headline":"Path Traversal in Splunk App for Lookup File Editing","id":"CVE-2023-32714"},"products":["Splunk App for Lookup File Editing"],"published":"2023-06-01","related":[{"cvss_score":2.5,"headline":"Incorrect permissions set by the “chmod“ and “makedirs“ Python functions in Splunk App for Lookup File Editing","id":"CVE-2025-20233","kev_date_added":null,"published":"2025-03-26"}],"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-02-28","vendors":["Splunk"]},"summary":"Attackers can execute malicious JavaScript on a victim's machine via self-XSS in the Splunk App for Lookup File Editing, requiring user interaction.","url":"https://insights.sbomify.com/CVE-2023-32715/"}