VulnerabilityPublished 3 Dec 2025

CVE-2025-20382: Splunk Enterprise · A web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a Redirect. This simplifies phishing attacks.

Affects Splunk EnterpriseSource CVE Database V5

Not known to be exploited · CVSS 3.5 Low.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

3.5Low

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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 3 Dec 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 26 Oct 2026.

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 =10.0 =9.4 =9.3 =9.2	Fixed in–

AI-suggested

1. Upgrade affected Splunk Enterprise and Splunk Cloud Platform instances to the patched versions: 10.0.2 or later for Enterprise, and 10.1.2507.10 or later for Cloud. 2. Restrict the ability to create or modify dashboards with custom backgrounds to trusted users only, minimizing the risk of malicious dashboard creation. 3. Implement strict content security policies (CSP) and URL filtering on Splunk dashboards to prevent loading or redirecting to untrusted external URLs. 4. Educate users about phishing risks, especially regarding unexpected redirects from internal dashboards or monitoring tools. 5. Monitor Splunk logs for unusual dashboard creation or modification activities by low-privileged users. 6. Use multi-factor authentication (MFA) to reduce the risk of compromised credentials being used in phishing attacks. 7. Consider network segmentation and web proxy controls to block access to known malicious external sites that could be used in redirects. These measures go beyond generic patching by focusing on reducing the attack surface and improving detection and response capabilities.

Description

In Splunk Enterprise versions below 10.0.2, 9.4.6, 9.3.8, and 9.2.10, and Splunk Cloud Platform versions below 10.1.2507.10, 10.0.2503.8, and 9.3.2411.120, a low-privileged user that does not hold the "admin" or "power" Splunk roles could create a views dashboard with a custom background using the `data:image/png;base64` protocol that could potentially lead to an unvalidated redirect. This behavior circumvents the Splunk external URL warning mechanism by using a specially crafted URL, allowing for a redirection to an external malicious site. The vulnerability requires the attacker to phish the victim by tricking them into initiating a request within their browser. The authenticated user should not be able to exploit the vulnerability at will.

Impact

For European organizations, the primary impact of CVE-2025-20382 is an increased risk of phishing attacks leveraging trusted Splunk dashboards to redirect users to malicious external sites. This could lead to credential theft, malware installation, or further social engineering attacks. Since Splunk is widely used in security monitoring, IT operations, and critical infrastructure sectors, a successful phishing campaign exploiting this vulnerability could undermine trust in security dashboards and potentially expose sensitive operational data indirectly. The vulnerability does not allow direct system compromise or data integrity violations but can facilitate lateral attack vectors through phishing. Organizations in sectors such as finance, energy, telecommunications, and government, which heavily rely on Splunk for monitoring and incident response, could face elevated risks. The requirement for authenticated access and user interaction limits the scope but does not eliminate the threat, especially in environments with many users having low-privileged Splunk accounts.

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Dec 2025, 18:34 UTC

Technical details

References

Community reviews

Related threats