CVE-2011-4642: mappy.py in Splunk Web in Splunk 4.2.x before 4.2.5 does not properly restrict use of the mappy command to...

Security readout for executives and security teams

This flaw affects legacy Splunk Web in Splunk 4.2.x before 4.2.5. An authenticated administrator could be made to trigger arbitrary code execution through the search application, including via CSRF. Business urgency depends on whether any old Splunk 4.2.x systems remain reachable. Exposure is likely limited to organizations still running Splunk 4.2.x before 4.2.5, especially where Splunk Web is reachable by administrators through browsers. The provided affected metadata is incomplete, but the CVE description identifies Splunk Web/Splunk 4.2.x. Prioritize this if legacy Splunk 4.2.x is still present. Arbitrary code execution in a monitoring platform can affect sensitive logs and operational visibility, but risk is reduced if no affected legacy instance exists. Mitigation focus: Upgrade Splunk 4.2.x installations to 4.2.5 or later per vendor guidance.; Restrict network access to Splunk Web administration interfaces.; Review vendor advisory SPL-45172 for supported remediation details..

Prepared

Jun 27, 2026, 17:28 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.