Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2023-32707: Privilege Escalation in Splunk Enterprise and Splunk Cloud via edit_user Capability

Published Jun 1, 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.
CVSS8.8High · v3.1
EPSS78.7%100th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Splunk
IdentifiersCVE-2023-32707CWE-269

CVE-2023-32707 is a privilege escalation vulnerability affecting Splunk Enterprise versions earlier than 9.0.5, 8.2.11, and 8.1.14, and Splunk Cloud Platform versions earlier than 9.0.2303.100. A low-privileged authenticated user assigned a role that includes the edit_user capability can escalate privileges to the admin user by sending specially crafted web requests. The flaw allows abuse of user-management functionality intended for delegated administration, resulting in unauthorized elevation from a limited role to full administrative access within 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 allows an authenticated low-privileged user to obtain administrative privileges in the affected Splunk deployment. This can result in full control of the Splunk environment, including unauthorized administrative actions, access to sensitive data managed by the platform, and increased risk of broader compromise or data breach.

Mitigation

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

Until patched, restrict assignment of the edit_user capability to only fully trusted administrative roles, review role configurations to remove unnecessary delegated user-management permissions, and monitor audit logs for suspicious password or user-management activity indicative of attempted privilege escalation. Limiting access to administrative web functionality and closely reviewing privileged role delegation can reduce exposure, but upgrading to fixed versions is the definitive mitigation.

Remediation

Patch, then assume compromise.

Upgrade Splunk Enterprise to version 9.0.5, 8.2.11, 8.1.14, or later, and upgrade Splunk Cloud Platform to version 9.0.2303.100 or later. Apply the vendor-provided fixes across all affected deployments and verify that no systems remain on vulnerable releases.

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-32707 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2023-32707 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2023-32707?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2023-32707, the earliest disclosed Jun 1, 2023.
Is there a patch for CVE-2023-32707?
Upgrade Splunk Enterprise to version 9.0.5, 8.2.11, 8.1.14, or later, and upgrade Splunk Cloud Platform to version 9.0.2303.100 or later. Apply the vendor-provided fixes across all affected deployments and verify that no systems remain on vulnerable releases.
What products are affected by CVE-2023-32707?
Splunk and Splunk Cloud Platform.
How severe is CVE-2023-32707?
CVE-2023-32707 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 78.7% (100th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
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 signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.