# CVE-2024-6878: Directory Browsing in Eliz Software's Panel

> Attackers can access files and directories externally to collect data from common resource locations in the Eliz Software Panel.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2024
- **Updated:** 3 Jun 2026
- **Also known as:** GHSA-q247-wj3r-2x97

## What is CVE-2024-6878?

CVE-2024-6878 is a critical vulnerability in Eliz Software Panel, published on 18 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Files or Directories Accessible to External Parties vulnerability in Eliz Software Panel allows Collect Data from Common Resource Locations.

This issue affects Panel: before v2.3.24.

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

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


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

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

## Is CVE-2024-6878 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-6878 is a critical vulnerability in Eliz Software Panel, published on 18 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-6878 in the wild and no public exploit code.

Affected product: Eliz Software Panel. 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-6878/ (Markdown: https://insights.sbomify.com/CVE-2024-6878/index.md)
```

## Sources

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

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