Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2023-22933: Cross-Site Scripting in Splunk Enterprise XML Views

Published Feb 14, 2023 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS6.1Medium · v3.1
EPSS0.83%58th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Splunk
IdentifiersCVE-2023-22933CWE-79 · Improper Neutralization of Input…

CVE-2023-22933 is a cross-site scripting vulnerability in Splunk Enterprise affecting versions earlier than 8.1.13, 8.2.10, and 9.0.4. The flaw exists in XML Views and is triggered through the layoutPanel attribute within a module tag. An attacker able to introduce a crafted XML View can cause malicious script to execute in the context of the Splunk Web interface when the affected view is rendered. This can expose users of the Splunk Web application to client-side code execution within their authenticated browser session and can create a path to further compromise of the Splunk environment.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation enables unauthorized script execution in a victim's browser within the Splunk Web context. This can lead to theft of sensitive data visible to the user, session hijacking, execution of actions as the victim within the application, and follow-on abuse of the Splunk environment depending on the victim's privileges.

Mitigation

If you can’t patch tonight, do this now.

Apply the vendor security update referenced in Splunk's February 2023 security guidance. Until patching is completed, restrict the ability to create or modify XML Views to trusted administrators only, review existing custom XML Views for unsafe use of the layoutPanel attribute in module tags, and avoid opening untrusted or recently modified views in the Splunk Web interface.

Remediation

Patch, then assume compromise.

Upgrade Splunk Enterprise to a fixed release. Vendor-fixed versions are 8.1.13 and later, 8.2.10 and later, and 9.0.4 and later. Where applicable, Splunk Cloud Platform should be updated to a fixed vendor release as identified in the corresponding security bulletin.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
SplunkSplunkapplication
SplunkSplunk Cloud Platformapplication
FAQ

Frequently asked questions

Is CVE-2023-22933 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2023-22933 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2023-22933?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2023-22933.
Is there a patch for CVE-2023-22933?
Upgrade Splunk Enterprise to a fixed release. Vendor-fixed versions are 8.1.13 and later, 8.2.10 and later, and 9.0.4 and later.
What products are affected by CVE-2023-22933?
Splunk and Splunk Cloud Platform.
How severe is CVE-2023-22933?
CVE-2023-22933 has a CVSS v3.1 score of 6.1 (Medium) and an EPSS score of 0.83% (58th percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.