dbcve.org
CommerceApplication · Adobe

CVE-2024-39397

CRITICAL · 9.0 CVSS v3.1 Published 2024-08-14
Fix available
A fix is available. Upgrade to after 2.4.3 or later.
See remediation →
99/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Adobe Commerce versions 2.4.7-p1, 2.4.6-p6, 2.4.5-p8, 2.4.4-p9 and earlier are affected by an Unrestricted Upload of File with Dangerous Type vulnerability that could result in arbitrary code execution by an attacker. An attacker could exploit this vulnerability by uploading a malicious file which can then be executed on the server. Exploitation of this issue does not require user interaction, but attack complexity is high and scope is changed.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Unrestricted file upload vulnerability in Adobe Commerce allows attackers to upload malicious files that can be executed on the server, leading to arbitrary code execution. The vulnerability affects multiple versions (2.4.4-p9 through 2.4.7-p1 and earlier) and can be exploited without user interaction, though attack complexity is high.

MitigationApply Adobe's official security patch for this vulnerability and update to a supported version. Additionally, implement file type validation, store uploads outside the webroot, and disable script execution in upload directories.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CommerceApplication
Affected:<= 2.4.3= 2.4.4= 2.4.5= 2.4.6= 2.4.7
MagentoCMS
Affected:<= 2.4.3= 2.4.4= 2.4.5= 2.4.6= 2.4.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Adobe Commerce or Magento version
    Check the version.php file in the app directory (app/etc/app.xml or lib/internal/Magento/Framework/App/Framework.php) or run: php bin/magento --version
    Affected if Installed version is 2.4.4 through 2.4.7 or 2.4.3 and below (specifically versions <= 2.4.3, = 2.4.4, = 2.4.5, = 2.4.6, = 2.4.7, or 2.4.4-p9 through 2.4.7-p1)
  2. Identify file upload functionality in use
    Review the codebase for file upload forms or endpoints, particularly in customer-facing modules. Search for form elements with type='file' or references to move_uploaded_file or similar file handling functions.
    Affected if The application accepts file uploads from unauthenticated or low-privilege users through any module
  3. Locate configured upload directories
    Check the media directory (pub/media) and any custom upload paths in configuration files (app/etc/env.php, admin panel Media settings). Look for directories configured for user-submitted content.
    Affected if Upload directories exist within the web-accessible document root (pub/media or similar)
  4. Verify script execution restrictions on upload directories
    Check for .htaccess rules or server configuration (Nginx/Apache) that disable PHP/script execution in upload directories. Examine .htaccess files in pub/media and similar upload folders.
    Affected if No restrictions are configured, or script execution is permitted in upload directories

You are affected if your installed Adobe Commerce/Magento version falls within 2.4.4 through 2.4.7 or is 2.4.3 and below, AND your application accepts file uploads to web-accessible directories without proper script execution restrictions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2.4.3
Interim mitigation

Apply Adobe's official security patch for this vulnerability and update to a supported version. Additionally, implement file type validation, store uploads outside the webroot, and disable script execution in upload directories.

Recommended fix High confidence

Upgrade to 2.4.4-p9 / 2.4.5-p8 / 2.4.6-p6 / 2.4.7-p1 (whichever corresponds to your current minor version)

  1. Identify your current Adobe Commerce/Magento version by running: php bin/magento --version
  2. For Adobe Commerce 2.4.4: Apply security patch 2.4.4-p9 or upgrade to 2.4.4-p9 or later
  3. For Adobe Commerce 2.4.5: Apply security patch 2.4.5-p8 or upgrade to 2.4.5-p8 or later
  4. For Adobe Commerce 2.4.6: Apply security patch 2.4.6-p6 or upgrade to 2.4.6-p6 or later
  5. For Adobe Commerce 2.4.7: Apply security patch 2.4.7-p1 or upgrade to 2.4.7-p1 or later
  6. For versions <= 2.4.3: Upgrade to minimum 2.4.4-p9 or later
  7. Download patches from the Adobe Security Patch Bulletin at helpx.adobe.com
  8. Apply the patch following Adobe's standard patch application process: composer install, then apply patch file
Caveat Review Adobe Commerce release notes for patch-specific notes; patches are cumulative but test in staging first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Commerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-39397 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-39397 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data