Path Traversal in studio-42/elfinder (CVE-2023-35840)
Summary
Path traversal in studio-42/elfinder (CVE-2023-35840). Confidential information can be exposed externally. Mitigation: upgrade to 2.1.62 or later.
Original description
The description as published by the source.
Impact
Path Traversal vulnerability in PHP LocalVolumeDriver connector. This vulnerability can be exploited by allowing untrusted users to write to the local file system.
This issue was caused by incomplete validity checking of the supplied request parameters. That problem has been fixed in elFinder Version 2.1.62.
Patches
This vulnerability has been fixed in elFinder 2.1.62. Installation managers should update to the latest version as soon as possible.
Workarounds
If you cannot update for some reason, you must stop using it or prohibit writing to untrusted users.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2023-35840 has been found in studio-42/elfinder.
Confidential information can be exposed externally.
What to do: upgrade studio-42/elfinder to 2.1.62 or later.
If unsure, ask your IT team or search "studio-42/elfinder CVE-2023-35840" on the vendor's site.
CVE-2023-35840 (studio-42/elfinder) — CWE-22
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.1.62 — apply immediately
Workaround: If you cannot update for some reason, you must stop using it or prohibit writing to untrusted users.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in studio-42/elfinder.
Check the vendor advisory for the affected versions of studio-42/elfinder.
Severity: ?. Confidential information can be exposed externally.
Update to 2.1.62.
Workaround: If you cannot update for some reason, you must stop using it or prohibit writing to untrusted users.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'studio-42/elfinder' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'studio-42/elfinder' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
studio-42/elfinderを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
If you cannot update for some reason, you must stop using it or prohibit writing to untrusted users.パッチが適用されるまでの応急処置として、If you cannot update for some reason, you must stop using it or prohibit writing to untrusted users. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade studio-42/elfinder to 2.1.62ステージング環境で 2.1.62 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com