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.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains a single Metasploit module targeting CVE-2023-32707, a privilege escalation vulnerability in Splunk Enterprise. The exploit leverages the 'edit_user' capability assigned to a low-privileged user role, which allows the attacker to change the admin password due to improper enforcement of the 'grantableRoles' setting in Splunk's configuration. After escalating privileges, the module logs in as admin and uploads a malicious Splunk app to achieve remote code execution (RCE) on the server. The module supports both Linux/Unix and Windows targets and can deliver any Metasploit-compatible payload. The exploit interacts with Splunk's REST API endpoints over HTTPS (default port 8000, SSL enabled by default). The repository is structured as a single Ruby file within the Metasploit framework, making it a weaponized, ready-to-use exploit for penetration testers and red teamers.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.