dbcve.org
CommerceApplication · Adobe

CVE-2024-39399

HIGH · 7.7 CVSS v3.1 Published 2024-08-14
Fix available
A fix is available. Upgrade to after 2.4.3 or later.
See remediation →
83/100
Remediation priority · High
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. A low-privileged 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 · high confidence

Adobe Commerce contains a path traversal vulnerability allowing low-privileged attackers to read arbitrary files outside the restricted directory through improper pathname limitation. The vulnerability can be exploited without user interaction and affects multiple versions (2.4.4-p9 through 2.4.7-p1 and earlier).

MitigationApply the vendor-supplied patch or upgrade to a patched version (2.4.7-p2, 2.4.6-p7, 2.4.5-p9, or 2.4.4-p10 or later) to remediate the path traversal vulnerability.

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify the installed Adobe Commerce or Magento version
    Run the command: php bin/magento --version or check the composer.json file in the web root for the 'version' field
    Affected if Version is not visible or cannot be determined
  2. Compare the installed version against affected ranges
    Check if the version is <= 2.4.3, or equals 2.4.4, 2.4.5, 2.4.6, or 2.4.7. Also verify if the patch level is below p10 for 2.4.4, p9 for 2.4.5, p7 for 2.4.6, or p2 for 2.4.7
    Affected if Version falls within the affected list and patch level is below the fixed versions (2.4.4-p10, 2.4.5-p9, 2.4.6-p7, 2.4.7-p2 or later)
  3. Confirm the product is Adobe Commerce or Magento Open Source
    Check the admin panel footer or run: php bin/magento about to identify the exact product edition
    Affected if Product is Adobe Commerce or Magento Open Source (formerly Magento)

A system is affected if it runs Adobe Commerce or Magento Open Source version 2.4.4 through 2.4.7 (or 2.4.3 and earlier) without the vendor-supplied patch or upgrade to version 2.4.4-p10, 2.4.5-p9, 2.4.6-p7, or 2.4.7-p2 or later.

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 patch or upgrade to a patched version (2.4.7-p2, 2.4.6-p7, 2.4.5-p9, or 2.4.4-p10 or later) to remediate the path traversal vulnerability.

Recommended fix High confidence

Upgrade to Adobe Commerce/Magento 2.4.4-p10+, 2.4.5-p9+, 2.4.6-p7+, or 2.4.7-p2+

  1. 1. Identify your current Adobe Commerce/Magento version by running: bin/magento --version
  2. 2. For Magento/OpenSource users: Upgrade to version 2.4.4-p10 or later (if on 2.4.4.x), or 2.4.5-p9 or later (if on 2.4.5.x), or 2.4.6-p7 or later (if on 2.4.6.x), or 2.4.7-p2 or later (if on 2.4.7.x)
  3. 3. For Adobe Commerce (Cloud or On-Premise) users: Upgrade to the same patch versions as above, or request the security patch from Adobe
  4. 4. Run composer require magento/product-community-edition=<version> --no-update (replace <version> with the target version from step 2)
  5. 5. Run composer update to install the new version
  6. 6. Clear the cache: bin/magento cache:flush
  7. 7. Re-index if necessary: bin/magento indexer:reindex
  8. 8. Verify the upgrade was successful: bin/magento --version
Caveat Standard upgrade risks apply - test in staging environment before production deployment

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

Fix this in Commerce Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
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,416.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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