CVE-2011-4642

CVE-2011-4642 is a medium-severity vulnerability in Splunk with a CVSS 2.0 base score of 4.6. Its EPSS exploit-prediction score of 29% places it in the 98th percentile, indicating an elevated likelihood of exploitation. The underlying weakness is classified as CWE-352.

Key facts

Description

mappy.py in Splunk Web in Splunk 4.2.x before 4.2.5 does not properly restrict use of the mappy command to access Python classes, which allows remote authenticated administrators to execute arbitrary code by leveraging the sys module in a request to the search application, as demonstrated by a cross-site request forgery (CSRF) attack, aka SPL-45172.

Frequently asked questions

What is 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 access Python classes, which allows remote authenticated administrators to execute arbitrary code by leveraging the sys module in a request to the search application, as demonstrated by a cross-site request forgery (CSRF) attack, aka SPL-45172.
How severe is CVE-2011-4642?
CVE-2011-4642 has a CVSS 2.0 base score of 4.6, rated medium severity.
Is CVE-2011-4642 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 29% (98th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2011-4642?
CVE-2011-4642 primarily affects Splunk. In total, 5 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2011-4642?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2011-4642 published?
CVE-2011-4642 was published on 2012-01-03 and last updated on 2026-06-16.

References

Affected products (5)

More vulnerabilities in Splunk

All CVEs affecting Splunk →

Other CWE-352 (Cross-Site Request Forgery (CSRF)) vulnerabilities

Browse all CWE-352 (Cross-Site Request Forgery (CSRF)) vulnerabilities →