{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2023-46213 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-46213 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-46213 is a medium-severity cross-site scripting vulnerability in Splunk Splunk, published on 16 Nov 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-46213 and fix it if it is affected.\n\nWhat it is: CVE-2023-46213 is a medium-severity cross-site scripting vulnerability in Splunk Splunk, published on 16 Nov 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-46213 in the wild and no public exploit code.\n\nAffected product: Splunk Splunk. 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-46213/ (Markdown: https://insights.sbomify.com/CVE-2023-46213/index.md)","id":"CVE-2023-46213","markdown":"https://insights.sbomify.com/CVE-2023-46213/index.md","name":"CVE-2023-46213","record":{"aliases":["GHSA-vfv2-6xpw-mqmp"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Splunk Enterprise","requires_auth":"high_privilege","summary":"Attackers can execute unauthorized code in user browsers via ineffective escaping in the syntax highlighting feature of the search page.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Splunk","cpe":[{"product":"cloud","vendor":"splunk"},{"product":"splunk","vendor":"splunk"}],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/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 Splunk Enterprise versions below 9.0.7 and 9.1.2, ineffective escaping in the “Show syntax Highlighted” feature can result in the execution of unauthorized code in a user’s web browser.","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":"Cross-site Scripting (XSS) on “Show Syntax Highlighted” View in Search Page","id":"CVE-2023-46213","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"splunk:splunk","products":["splunk:splunk"],"type":"xss","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Remote code execution (RCE) in Splunk Enterprise through Insecure XML Parsing","id":"CVE-2023-46214"},"packages":[],"prev":{"headline":"WordPress WP EXtra Plugin \u003c= 6.2 is vulnerable to Broken Access Control","id":"CVE-2023-46212"},"products":["Splunk Cloud","Splunk Enterprise"],"published":"2023-11-16","related":[{"cvss_score":8,"headline":"Remote code execution (RCE) in Splunk Enterprise through Insecure XML Parsing","id":"CVE-2023-46214","kev_date_added":null,"published":"2023-11-16"},{"cvss_score":7.5,"headline":"Denial of Service through null pointer reference in “cluster/config” REST endpoint","id":"CVE-2024-36982","kev_date_added":null,"published":"2024-07-01"},{"cvss_score":6.5,"headline":"Low-privileged user could create notifications in Splunk Web Bulletin Messages","id":"CVE-2024-36989","kev_date_added":null,"published":"2024-07-01"},{"cvss_score":6.5,"headline":"Splunk App Key Value Store (KV Store) Improper Handling of Permissions Leads to KV Store Collection Deletion","id":"CVE-2024-23675","kev_date_added":null,"published":"2024-01-22"},{"cvss_score":6.3,"headline":"Risky command safeguards bypass through Search ID query in Analytics Workspace","id":"CVE-2024-36986","kev_date_added":null,"published":"2024-07-01"},{"cvss_score":4.6,"headline":"Sensitive Information Disclosure of Index Metrics through “mrollup” SPL Command","id":"CVE-2024-23676","kev_date_added":null,"published":"2024-01-22"}],"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":"total"},"state":"PUBLISHED","updated":"2025-02-28","vendors":["Splunk"]},"summary":"Attackers can execute unauthorized code in user browsers via ineffective escaping in the syntax highlighting feature of the search page.","url":"https://insights.sbomify.com/CVE-2023-46213/"}