CVE-2011-4642

What it is

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.

At a glance

Exploitability

Can be exploited over the network with a login. Limited direct impact.

Exploit odds

28.6% chance of exploitation in the next 30 days (EPSS). Higher than most.

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2012-01-03 11:55 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-16 23:35 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 28.6% in the next 30 days (EPSS).
• Severity: 4.6 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2012-01-03 11:55 UTC

Last modified

2026-06-16 23:35 UTC

Exploit probability

28.6% · EPSS, next 30 days

Weakness

CWE-352 · Cross-site request forgery

Record status

Modified

Affected

• Splunk 4.2
• Splunk 4.2.1
• Splunk 4.2.2
• Splunk 4.2.3
• Splunk 4.2.4

Attack profile CVSS 2.0 · 4.6

Attack vector

Network

Complexity

High

Authentication

Single

Confidentiality

Partial

Integrity

Partial

Availability

Partial

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2011-4642.md and follow it. Check whether this project is affected by CVE-2011-4642. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge