Path Traversal in studio-42/elfinder (CVE-2021-32682)
Summary
Path traversal in studio-42/elfinder (CVE-2021-32682). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2.1.59 or later.
Original description
The description as published by the source.
elFinder is an open-source file manager for web, written in JavaScript using jQuery UI. Several vulnerabilities affect elFinder 2.1.58. These vulnerabilities can allow an attacker to execute arbitrary code and commands on the server hosting the elFinder PHP connector, even with minimal configuration. The issues were patched in version 2.1.59. As a workaround, ensure the connector is not exposed without authentication.
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-2021-32682 has been found in studio-42/elfinder.
Successful exploitation can lead to full system takeover.
What to do: upgrade studio-42/elfinder to 2.1.59 or later.
If unsure, ask your IT team or search "studio-42/elfinder CVE-2021-32682" on the vendor's site.
CVE-2021-32682 (studio-42/elfinder) — CWE-22
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.1.59 — apply immediately
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: ?. Successful exploitation can lead to full system takeover.
Update to 2.1.59.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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 patch patch
Upgrade studio-42/elfinder to 2.1.59ステージング環境で 2.1.59 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- report packetstormsecurity.com
- report blog.sonarsource.com
- web github.com
- web blog.sonarsource.com