# CVE-2019-6257: elFinder Server Side Request Forgery (SSRF)

> A Server Side Request Forgery vulnerability in elFinder allows attackers to access internal network resources via the get_remote_contents function.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Jan 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-3qhm-qfj3-4rrx

## What is CVE-2019-6257?

CVE-2019-6257 is a high-severity server-side request forgery vulnerability in n/a, published on 14 Jan 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A Server Side Request Forgery (SSRF) vulnerability in elFinder before 2.1.46 could allow a malicious user to access the content of internal network resources. This occurs in get_remote_contents() in php/elFinder.class.php.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2019-6257?

2 open source packages ship an affected version, including studio-42/elfinder. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `studio-42/elfinder` | Packagist | All versions | 2.1.49 |
| `studio-42/elfinder` | Packagist | All versions | 2.1.49 |

Products: Std42 Elfinder.

## How do I fix CVE-2019-6257?

Upgrade studio-42/elfinder to 2.1.49 or later.

## Is CVE-2019-6257 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-52044](https://insights.sbomify.com/CVE-2023-52044/): File upload in n/a (critical 9.8)
- [CVE-2024-38909](https://insights.sbomify.com/CVE-2024-38909/): Studio 42 elFinder vulnerable to Incorrect Access Control (critical 9.8)
- [CVE-2022-27115](https://insights.sbomify.com/CVE-2022-27115/): RCE in Studio-42 elFinder on Windows before 2.1.61 (critical 9.8)
- [CVE-2021-43421](https://insights.sbomify.com/CVE-2021-43421/): elFinder Unrestricted File Upload vulnerability (critical 9.8)
- [CVE-2021-32682](https://insights.sbomify.com/CVE-2021-32682/): Multiple vulnerabilities leading to RCE (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-6257 and fix it if it is affected.

What it is: CVE-2019-6257 is a high-severity server-side request forgery vulnerability in n/a, published on 14 Jan 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-6257 in the wild and no public exploit code.

Affected packages and fixed versions:
- studio-42/elfinder (Packagist): affected all versions; fixed in 2.1.49
- studio-42/elfinder (Packagist): affected all versions; fixed in 2.1.49

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-2019-6257/ (Markdown: https://insights.sbomify.com/CVE-2019-6257/index.md)
```

## Sources

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

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