dbcve.org
CommerceApplication · Adobe

CVE-2024-39406

MEDIUM · 6.8 CVSS v3.1 Published 2024-08-14
Fix available
A fix is available. Upgrade to after 2.4.3 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable 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 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability that could lead to arbitrary file system read. An admin attacker could exploit this vulnerability to gain access to files and directories that are outside the restricted directory. Exploitation of this issue does not require user interaction 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 · moderate confidence

Adobe Commerce contains a path traversal vulnerability allowing an authenticated admin attacker to read arbitrary files outside the restricted directory. The vulnerability affects versions 2.4.4-p9 through 2.4.7-p1 and does not require user interaction.

MitigationApply the vendor-supplied security patches or upgrade to a patched version of Adobe Commerce (2.4.7-p2, 2.4.6-p7, 2.4.5-p9, or 2.4.4-p10 or later).

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
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

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

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. Check installed Adobe Commerce or Magento version
    Locate the composer.json file in the Magento root directory and read the 'version' field, or inspect the app/etc/config.php file which contains version metadata. Alternatively, log into the admin panel and view the footer for the version number.
    Affected if The installed version is 2.4.4, 2.4.5, 2.4.6, or 2.4.7, or any version 2.4.3 or lower.
  2. Confirm admin access exists
    Verify that the admin panel is accessible and that administrator accounts exist. Check the admin_users table in the database or attempt to access the admin login endpoint at /admin or /backend.
    Affected if An authenticated admin user account can be accessed or created in the system.
  3. Identify file operation modules accessible to admin
    Review the admin panel for any modules or features that allow file reading, export, or configuration file viewing. Look for any file management, configuration export, or data export functionalities available under System, Configuration, or Tools menus.
    Affected if An admin-accessible feature exists that processes file paths or allows reading configuration files.

You are affected if your Adobe Commerce or Magento installation version is 2.4.4 through 2.4.7 (or 2.4.3 and lower) and an authenticated admin user can access file reading functionality.

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 the vendor-supplied security patches or upgrade to a patched version of Adobe Commerce (2.4.7-p2, 2.4.6-p7, 2.4.5-p9, or 2.4.4-p10 or later).

Recommended fix High confidence

Adobe Commerce/Magento 2.4.4-p10, 2.4.5-p9, 2.4.6-p7, or 2.4.7-p2 (depending on your baseline branch)

  1. 1. Identify your current Adobe Commerce/Magento version using the command line: bin/magento --version
  2. 2. Review the Adobe Security Bulletin for CVE-2024-39406 at helpx.adobe.com to obtain the specific patch for your version
  3. 3. Backup your entire Magento database and codebase before applying any updates
  4. 4. For Adobe Commerce on-premises (2.4.4-p9 and below): Apply the security patch SUPEE-12457 or upgrade to 2.4.4-p10, 2.4.5-p9, 2.4.6-p7, or 2.4.7-p2 respectively
  5. 5. For Magento Open Source (2.4.4-p9 and below): Apply the equivalent patch or upgrade to the same patch versions
  6. 6. Clear the Magento cache after upgrade: bin/magento cache:clean
  7. 7. Verify the upgrade was successful: bin/magento --version
Caveat Patch updates are typically backward-compatible; however, always test in a staging environment as custom extensions may require adjustment for new patch versions

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

Fix this in Commerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-39406 — 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-39406 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