{"answers":{"affected":"It affects 2 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-46214 exists.","fix":"No fix has been published for CVE-2023-46214 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-46214 is a high-severity vulnerability in Splunk Splunk, published on 16 Nov 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-2023-46214 and fix it if it is affected.\n\nWhat it is: CVE-2023-46214 is a high-severity vulnerability in Splunk Splunk, published on 16 Nov 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-2023-46214 exists.\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-46214/ (Markdown: https://insights.sbomify.com/CVE-2023-46214/index.md)","id":"CVE-2023-46214","markdown":"https://insights.sbomify.com/CVE-2023-46214/index.md","name":"CVE-2023-46214","record":{"aliases":["GHSA-mwwq-v92j-38xr"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Splunk Enterprise","requires_auth":"low_privilege","summary":"Attackers can achieve remote code execution on Splunk Enterprise by uploading malicious XSLT files due to insecure XML parsing.","user_interaction":"required","vuln_class":"xxe"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Splunk","cpe":[{"product":"cloud","vendor":"splunk"},{"product":"splunk","vendor":"splunk"}],"cvss":{"score":8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-91","name":"XML Injection"}],"description":"In Splunk Enterprise versions below 9.0.7 and 9.1.2, Splunk Enterprise does not safely sanitize extensible stylesheet language transformations (XSLT) that users supply. This means that an attacker can upload malicious XSLT which can result in remote code execution on the Splunk Enterprise instance.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2023-11-28","github_poc":0,"max_poc_stars":null,"metasploit":1,"nuclei":0,"refs":[{"date":"2023-11-28","kind":"metasploit","ref":"exploit/unix/http/splunk_xslt_authenticated_rce","stars":null,"title":"Splunk Authenticated XSLT Upload RCE"}],"tier":"weaponised"},"has_fix":null,"headline":"Remote code execution (RCE) in Splunk Enterprise through Insecure XML Parsing","id":"CVE-2023-46214","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"splunk:splunk","products":["splunk:splunk"],"type":"xxe","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"Apache Airflow Celery provider Insertion of Sensitive Information into Log File vulnerability","id":"CVE-2023-46215"},"packages":[],"prev":{"headline":"Cross-site Scripting (XSS) on “Show Syntax Highlighted” View in Search Page","id":"CVE-2023-46213"},"products":["Splunk Cloud","Splunk Enterprise"],"published":"2023-11-16","related":[{"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.8,"headline":"Cross-site Scripting (XSS) on “Show Syntax Highlighted” View in Search Page","id":"CVE-2023-46213","kev_date_added":null,"published":"2023-11-16"},{"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)"},{"class":"attribution","licence":"BSD-3-Clause","name":"Metasploit"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-12-16","vendors":["Splunk"]},"summary":"Attackers can achieve remote code execution on Splunk Enterprise by uploading malicious XSLT files due to insecure XML parsing.","url":"https://insights.sbomify.com/CVE-2023-46214/"}