# CVE-2024-9142: Local File Inclusion (LFI) in Olgu Computer Systems' e-Belediye

> Attackers can manipulate web input to access unauthorized files or execute code in Olgu Computer Systems' e-Belediye municipal software.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Sep 2024
- **Updated:** 2 Jun 2026
- **Also known as:** GHSA-3ch5-8236-6hmm

## What is CVE-2024-9142?

CVE-2024-9142 is a critical path traversal vulnerability in Olgu Computer Systems e-Belediye, published on 24 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

External Control of File Name or Path, : Incorrect Permission Assignment for Critical Resource vulnerability in Olgu Computer Systems e-Belediye allows Manipulating Web Input to File System Calls.

This issue affects e-Belediye: before 2.0.642.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource), CWE-73 (External Control of File Name or Path)

## Which versions are affected by CVE-2024-9142?


## How do I fix CVE-2024-9142?

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

## Is CVE-2024-9142 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-9142 and fix it if it is affected.

What it is: CVE-2024-9142 is a critical path traversal vulnerability in Olgu Computer Systems e-Belediye, published on 24 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-9142 in the wild and no public exploit code.

Affected product: Olgu Computer Systems e-Belediye. 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-2024-9142/ (Markdown: https://insights.sbomify.com/CVE-2024-9142/index.md)
```

## Sources

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

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