CVE-2023-22940Network attack vector

Indexed-data exposure via unsafeguarded SPL aliases

Published Feb 14, 2023 · Updated Feb 28, 2025

Improper input validation in Splunk Web allows attackers to expose indexed data through affected Splunk Enterprise and Cloud Platform releases. The collect command aliases lack the safeguarded-command designation, allowing a privileged search context to write confidential results into a summary index readable by less-privileged accounts. Exploitation requires Splunk Web and a higher-privileged user to initiate a browser request; the consequence is bounded to disclosure and limited writes in summary indexes.

CVSS severity6.3
Medium
EPSS probability0.43%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper input validation in Splunk Web allows attackers to expose indexed data through affected Splunk Enterprise and Cloud Platform releases. The collect command aliases lack the safeguarded-command designation, allowing a privileged search context to write confidential results into a summary index readable by less-privileged accounts. Exploitation requires Splunk Web and a higher-privileged user to initiate a browser request; the consequence is bounded to disclosure and limited writes in summary indexes.

The record

CVE
CVE-2023-22940
Published
Feb 14, 2023
Updated
Feb 28, 2025
Vendor
Splunk, Inc.
Product
Splunk Enterprise
Classifications
CWE-20, T1213
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Feb 14, 2023CVE publishedPublication date reported by the CVE source.
  2. Feb 28, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=8.1 <8.1.13
  2. Affected versionversion=8.2 <8.2.10
  3. Affected versionversion=9.0 <9.0.4

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Splunk, Inc. · Splunk Enterpriseversion=8.1 <8.1.13; version=8.2 <8.2.10; version=9.0 <9.0.4
Splunk, Inc. · Splunk Cloud Platformversion=- <9.0.2212

Published CVSS scores

6.3Splunk Inc.CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:N
5.7NIST NVDCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-20Improper Input Validation
T1213Data from Information Repositories

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo