Security readout for executives and security teams
Plain-English summary
This CVE describes a remote file upload flaw in Studio-42 elFinder versions 2.0.4 through 2.1.59. The reported impact is serious: an attacker could upload arbitrary files and execute PHP code. The source bundle does not include a CVSS score, confirmed patch version, or evidence of active exploitation.
Executive priority
Treat this as high priority if elFinder is externally reachable. Remote PHP execution can create full application compromise, but urgency depends on whether affected versions and connector exposure exist in the environment.
Technical view
The issue is reported in elFinder through connector.minimal.php, where arbitrary file upload can lead to PHP code execution. The CVE data identifies affected versions as 2.0.4 to 2.1.59, but lacks CWE, CVSS, and detailed vendor remediation metadata. KEV status is false in the bundle.
Likely exposure
Exposure is most likely where elFinder 2.0.4 through 2.1.59 is deployed with connector.minimal.php reachable by remote users, especially on PHP-enabled web servers.
Exploitation context
The bundle does not show CISA KEV listing or confirmed exploitation in the wild. Public references exist, including a GitHub issue and Twitter post, but the provided evidence only supports public disclosure, not active exploitation.
Researcher notes
The source bundle is thin: no CVSS, CWE, exploit maturity detail, or official remediation text is provided. Assessment relies mainly on the CVE description and public references. Avoid assuming a specific patched version without vendor confirmation.
Mitigation direction
- Inventory elFinder deployments and identify versions 2.0.4 through 2.1.59.
- Check Studio-42 elFinder guidance for fixed versions or official hardening steps.
- Restrict public access to elFinder connectors where business use does not require it.
- Prevent uploaded content from being executed as PHP on the hosting server.
- Review web server logs for suspicious elFinder connector access.
Validation and detection
- Confirm whether connector.minimal.php exists in deployed elFinder paths.
- Verify deployed elFinder versions against the 2.0.4 to 2.1.59 range.
- Check whether elFinder connector endpoints are internet-accessible.
- Review upload directories for unexpected executable PHP content.
- Validate that upload locations cannot execute server-side code.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
File access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-43421 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/Studio-42/elFinder/issues/3429CVE reference · x_refsource_MISC
- https://twitter.com/infosec_90/status/1455180286354919425CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.