CVE-2019-6257 json
elFinder Server Side Request Forgery (SSRF)
published 7y ago modified 4mo ago also GHSA-3qhm-qfj3-4rrx , EUVD-2022-2234
- cvss
- 7.7
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 65%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- packagist studio-42/elfinder 2.1.49
- std42 elfinder 2.1.46
Is CVE-2019-6257 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.10% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.7 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
| GitHub | 3.1 | 7.7 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | studio-42/elfinder | <2.1.49 |
2.1.49 |
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
-
github.com
/Studio-42/elFinder/commit/2f522db8f037a66ce9040ee0b216aa4a0359286c
web, patch, third-party-advisory
-
github.com
/Studio-42/elFinder/blob/68ec63c0aeca3963101aca8f842dc9f2e4c4c6d3/Changelog
third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-6257
advisory
-
github.com
/FriendsOfPHP/security-advisories/blob/master/studio-42/elfinder/CVE-2019-6257.yaml
web
-
github.com
/Studio-42/elFinder
package
-
github.com
/Studio-42/elFinder/blob/2.1.49/Changelog
web
-
github.com
/Studio-42/elFinder/releases/tag/2.1.49
web
Sources
- CVE List CVE-2019-6257
- GitHub Advisory GHSA-3qhm-qfj3-4rrx
- NVD CVE-2019-6257
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.