CVE-2025-20297VulnerabilityPublished 2 Jun 2025

CVE-2025-20297: Splunk Enterprise · The software does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

Affects Splunk EnterpriseSource CVE Database V5

Not known to be exploited · 29% EPSS · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 29.3% chance of exploitation in 30 days – higher than 98% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Splunk Splunk Enterprise	Affected =9.4 =9.3 =9.2 =9.1	Fixed in–

AI-suggested

European organizations should prioritize upgrading affected Splunk Enterprise and Cloud Platform instances to versions 9.4.2, 9.3.4, or 9.2.6 or later, where the vulnerability is patched. Until patches are applied, organizations should restrict access to the pdfgen/render REST endpoint to trusted users only, ideally limiting it to admin or power roles. Implementing strict role-based access controls (RBAC) and monitoring for unusual activity on this endpoint can reduce exploitation risk. Web application firewalls (WAFs) with custom rules to detect and block suspicious payloads targeting the pdfgen/render endpoint may provide temporary protection. Additionally, organizations should educate users about the risks of XSS and encourage cautious behavior when interacting with Splunk-generated content. Regular security audits and penetration testing focusing on Splunk deployments can help identify residual risks. Finally, logging and alerting on REST endpoint usage can facilitate early detection of exploitation attempts.

Description

In Splunk Enterprise versions below 9.4.2, 9.3.4 and 9.2.6, and Splunk Cloud Platform versions below 9.3.2411.102, 9.3.2408.111 and 9.2.2406.118, a low-privileged user that does not hold the "admin" or "power" Splunk roles could craft a malicious payload through the pdfgen/render REST endpoint that could result in execution of unauthorized JavaScript code in the browser of a user.

Impact

For European organizations, this vulnerability poses a risk primarily to confidentiality due to potential unauthorized JavaScript execution in user browsers. Organizations using Splunk Enterprise or Splunk Cloud Platform for log management and security analytics could see targeted attacks aiming to compromise user sessions or exfiltrate sensitive information. Since the vulnerability requires only low privileges and no user interaction, insider threats or compromised low-privileged accounts could be leveraged to escalate attacks. The impact is heightened in sectors with stringent data protection regulations such as GDPR, where unauthorized data exposure can lead to regulatory penalties and reputational damage. Additionally, organizations relying heavily on Splunk dashboards and reports for security monitoring may face risks of manipulated or misleading information if attackers inject malicious scripts. However, the vulnerability does not affect system integrity or availability directly, limiting its impact to confidentiality breaches and potential session hijacking or phishing within the Splunk user base.

References

advisory.splunk.com/advisories/SVD-2025-0601 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Jul 2025, 07:50 UTC

Technical details

References

Community reviews

Related threats