Splunk Enterprise Flaws Allow Attackers to Run Unauthorized JavaScript Code
Splunk has issued security advisories to address multiple vulnerabilities affecting Splunk Enterprise and Splunk Cloud Platform versions.
Splunk has issued security advisories to address multiple vulnerabilities affecting Splunk Enterprise and Splunk Cloud Platform versions.
The identified vulnerabilities include cross-site scripting (XSS) and access control issues, with Common Vulnerability Scoring System (CVSS) scores ranging from 4.6 to 7.5.
Six vulnerabilities were identified, primarily affecting the Splunk Web components. Two XSS vulnerabilities allow low-privileged users to execute malicious JavaScript in victim browsers.
CVE-2025-20366: Improper Access Control - CVSS 6.5 (Medium) CVE-2025-20367: Reflected XSS - CVSS 5.7 (Medium) CVE-2025-20368: Stored XSS - CVSS 5.7 (Medium) CVE-2025-20369: XML External Entity (XXE) - CVSS 4.6 (Medium) CVE-2025-20370: Denial of Service (DoS) - CVSS 4.9 (Medium) CVE-2025-20371: Server-Side Request Forgery (SSRF) - CVSS 7.5 (High)
Splunk has issued security advisories to address multiple vulnerabilities affecting Splunk Enterprise and Splunk Cloud Platform versions.
The most severe, CVE-2025-20371, involves an unauthenticated blind server-side request forgery that can make REST API calls on behalf of high-privileged users under certain conditions.
These vulnerabilities affect Splunk Enterprise versions below 9.4.4, 9.3.6, and 9.2.8, and specific builds of Splunk Cloud Platform. Splunk Enterprise 10.0.0 is vulnerable to LDAP DoS and SSRF attacks but not to XSS and access control issues. Most vulnerabilities target Splunk Web, except the SSRF, which affects the REST API.
Upgrade to the latest patched versions: 10.0.1, 9.4.4, 9.3.6, or 9.2.8 for Splunk Enterprise. For immediate protection, disable Splunk Web, though this may affect functionality. Mitigate SSRF risk by setting enableSplunkWebClientNetloc to false in web.conf . Address LDAP DoS by removing change_authentication capability from non-essential user roles.
Organizations should ensure Splunk installations are up-to-date and implement access controls. Regularly review user privileges and monitor search job access patterns. Conduct security assessments to identify potential vulnerabilities.
Input validation and output encoding are critical to prevent XSS in web applications handling user-generated content.
Based on reporting by GBHackers.
