# CVE-2025-20233: Incorrect permissions set by the “chmod“ and “makedirs“ Python functions in Splunk App for Lookup File Editing

> A low-privileged user can access files with overly broad permissions due to incorrect chmod and makedirs usage in the Splunk App for Lookup File Editing.

- **Severity:** Low 2.5 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Mar 2025
- **Updated:** 27 Mar 2025
- **Also known as:** GHSA-x67m-xw25-vpg2

## What is CVE-2025-20233?

CVE-2025-20233 is a low-severity vulnerability in Splunk App for Lookup File Editing, published on 26 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Splunk App for Lookup File Editing versions below 4.0.5, a script in the app used the `chmod` and `makedirs` Python functions in a way that resulted in overly broad read and execute permissions. This could lead to improper access control for a low-privileged user.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2025-20233?

It affects 1 product.


Products: Splunk Splunk App for Lookup File Editing.

## How do I fix CVE-2025-20233?

No fix has been published for CVE-2025-20233 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-20233 being exploited?

There is no known exploitation of CVE-2025-20233 in the wild and no public exploit code.

## Other vulnerabilities in Splunk App for Lookup File Editing

- [CVE-2023-32715](https://insights.sbomify.com/CVE-2023-32715/): Self Cross-Site Scripting (XSS) on Splunk App for Lookup File Editing (medium 4.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-20233 and fix it if it is affected.

What it is: CVE-2025-20233 is a low-severity vulnerability in Splunk App for Lookup File Editing, published on 26 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-20233 in the wild and no public exploit code.

Affected product: Splunk App for Lookup File Editing. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-20233/ (Markdown: https://insights.sbomify.com/CVE-2025-20233/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-20233
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-20233
- OSV: https://osv.dev/vulnerability/CVE-2025-20233

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-20233/
Summaries are generated and may contain mistakes; the official description above is the record.