# CVE-2024-4836: LFI in sites managed by Edito CMS

> Unauthenticated attackers can download sensitive configuration files from Edito CMS installations, leading to information disclosure.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jul 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-w2w9-635q-99v6

## What is CVE-2024-4836?

CVE-2024-4836 is a high-severity path traversal vulnerability in Edito CMS, published on 2 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Web services managed by Edito CMS (Content Management System) in versions from 3.5 through 3.25 leak sensitive data as they allow downloading configuration files by an unauthenticated user.
The issue in versions 3.5 - 3.25 was removed in releases which dates from 10th of January 2014. Higher versions were never affected.

Weakness: CWE-552 (Files or Directories Accessible to External Parties)

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


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

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

## Is CVE-2024-4836 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-4836 exists.

Public exploit code:

- Edito CMS - Sensitive Data Leak (nuclei): http/cves/2024/CVE-2024-4836.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2024-4836 is a high-severity path traversal vulnerability in Edito CMS, published on 2 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-4836 exists.

Affected product: Edito CMS. 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-4836/ (Markdown: https://insights.sbomify.com/CVE-2024-4836/index.md)
```

## Sources

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

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