CVE-2025-20382
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA low-privileged Splunk user (non-admin, non-power) can create a views dashboard with a custom background using the data:image/png;base64 protocol, which circumvents Splunk's external URL warning mechanism. This allows redirection to malicious external sites through specially crafted URLs, requiring phishing the victim to initiate a request.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 9.2.0, < 9.2.10>= 9.3.0, < 9.3.8>= 9.4.0, < 9.4.6>= 10.0.0, < 10.0.2>= 9.3.2411, < 9.3.2411.120>= 10.0.2503, < 10.0.2503.8>= 10.1.2507, < 10.1.2507.10CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Splunk product and versionRun `splunk version` on the Splunk Enterprise instance, or check the Cloud Platform version through the Splunk Cloud UI under About > Version. Compare the installed version against the affected ranges: Splunk Enterprise 9.2.0 to 9.2.9, 9.3.0 to 9.3.7, 9.4.0 to 9.4.5, and 10.0.0 to 10.0.1 are vulnerable. Splunk Cloud Platform versions below 9.3.2411.120, below 10.0.2503.8, and below 10.1.2507.10 are vulnerable.Affected if The installed version falls within any of the vulnerable version ranges listed.
-
Locate dashboards using data: URI backgroundsSearch Splunk configuration files (*.conf) or saved searches/views for the string 'data:image/png;base64' in the views or dashboard XML configuration files. On Splunk Enterprise, these are typically stored in $SPLUNK_HOME/etc/users/*/data/ui/views/ or can be exported via the REST endpoint /servicesNS/-/-/data/ui/views/.Affected if Any dashboard or view XML contains the data:image/png;base64 URI scheme for a custom background image.
-
Check for external URL redirection patternsExamine dashboard or view configurations for external URL references that could be used for phishing redirection. Look for href, link, or redirect parameters pointing to external domains, particularly in conjunction with base64-encoded image data. Review the Simple XML source of dashboards via the UI or REST API.Affected if Dashboards contain external URL references combined with data: URI backgrounds that could enable phishing redirects.
You are affected if your Splunk version is within the vulnerable ranges AND low-privileged users have the ability to create or modify dashboards with custom background images using the data: URI scheme.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped9.2.109.3.89.3.2411.120
Upgrade Splunk Enterprise to version 10.0.2, 9.4.6, 9.3.8, or 9.2.10 and above, or upgrade Splunk Cloud Platform to version 10.1.2507.10, 10.0.2503.8, or 9.3.2411.120 and above to remediate this vulnerability.
Splunk Enterprise: 9.2.10, 9.3.8, 9.4.6, or 10.0.2 (depending on current branch); Splunk Cloud Platform: 9.3.2411.120, 10.0.2503.8, or 10.1.2507.10
- Identify the currently installed Splunk Enterprise or Splunk Cloud Platform version using the Splunk Web interface (Settings > Server settings > About Splunk) or the CLI: 'splunk version'
- For Splunk Enterprise: Plan upgrade to the minimum fixed version for your current major release branch: 9.2.10, 9.3.8, 9.4.6, or 10.0.2
- For Splunk Cloud Platform: Contact Splunk Cloud support to schedule the upgrade to the fixed version: 9.3.2411.120, 10.0.2503.8, or 10.1.2507.10
- Review Splunk Release Notes for the target version for any breaking changes or migration requirements
- Test the upgrade in a non-production environment before deploying to production
- Back up your Splunk configuration and data directory before initiating the upgrade
- Execute the upgrade following Splunk's official upgrade documentation
- Verify the upgrade was successful and the Splunk services are running correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20382 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-20382 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data