dbcve.org
CommerceApplication · Adobe

CVE-2025-24406

HIGH · 7.5 CVSS v3.1 Published 2025-02-11
Fix available
A fix is available. Upgrade to 1.3.3 / 2.4.4 or later.
See remediation →
84/100
Remediation priority · High
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.8-beta1, 2.4.7-p3, 2.4.6-p8, 2.4.5-p10, 2.4.4-p11 and earlier are affected by an Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability that could lead to a security feature bypass. An unauthenticated attacker could exploit this vulnerability to modify files that are stored outside the restricted directory. Exploitation of this issue does not require user interaction.

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 unauthenticated attackers to modify files outside restricted directories by manipulating file path inputs. This security feature bypass affects versions 2.4.8-beta1 through 2.4.4-p11 and earlier, requiring no user interaction for exploitation.

MitigationApply the appropriate Adobe Commerce security patch or upgrade to a fixed version as specified in the Adobe security bulletin. Review file access controls and implement proper path validation to prevent directory traversal.

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.4= 2.4.4= 2.4.5= 2.4.6= 2.4.7= 2.4.8
Commerce B2bApplication
Affected:< 1.3.3= 1.3.3= 1.3.4= 1.3.5= 1.4.2= 1.5.0
MagentoCMS
Affected:< 2.4.4= 2.4.4= 2.4.5= 2.4.6= 2.4.7= 2.4.8

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 if Adobe Commerce or Magento is installed
    Locate the Magento installation directory and check for the presence of the composer.json file or the magento folder in the web root. Alternatively, access the admin panel or check the footer of the storefront for the 'Powered by Magento' text.
    Affected if The software is Adobe Commerce, Adobe Magento, or Adobe Commerce B2b.
  2. Determine the installed Adobe Commerce or Magento version
    Open the file 'composer.json' in the Magento root directory and look for the 'version' field, or access the admin panel and navigate to System > Tools > Web Setup Wizard, or check the file app/etc/di.xml for version information.
    Affected if The installed version matches or falls within the affected ranges: Adobe Commerce versions < 2.4.4, = 2.4.4, = 2.4.5, = 2.4.6, = 2.4.7, = 2.4.8 (including 2.4.8-beta1 through 2.4.4-p11); Adobe Magento versions < 2.4.4, = 2.4.4, = 2.4.5, = 2.4.6, = 2.4.7, = 2.4.8; Adobe Commerce B2b versions < 1.3.3,
  3. Check for the presence of Adobe Commerce B2b extension version
    If Adobe Commerce is installed, check the composer.json file or the app/code/Magento/ directory for the B2b extension, and run 'composer show magento/module-b2b' to list the installed B2b version.
    Affected if The B2b extension version matches or falls within: < 1.3.3, = 1.3.3, = 1.3.4, = 1.3.5, = 1.4.2, = 1.5.0.
  4. Verify web server and PHP configuration allows file operations
    Review the web server configuration and PHP settings to confirm that file upload and write operations are permitted in the Magento web root directories.
    Affected if The web server has write permissions to directories that handle user-supplied file paths, enabling the path traversal vulnerability to be exploited.
  5. Audit access logs for suspicious path traversal patterns
    Search web server access logs (typically in /var/log/apache2/, /var/log/nginx/, or /var/log/httpd/) for requests containing patterns like '../', '..\', or encoded path sequences targeting files outside the Magento root.
    Affected if Logs contain unauthenticated requests with directory traversal sequences targeting sensitive files outside the Magento installation directory.

A defender is affected if their environment runs Adobe Commerce, Adobe Magento, or Adobe Commerce B2b with a version number that matches the affected ranges listed, and the vulnerable path handling functionality is accessible without authentication.

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 1.3.3 / 2.4.4 or later
Fixed in 1.3.32.4.4
Interim mitigation

Apply the appropriate Adobe Commerce security patch or upgrade to a fixed version as specified in the Adobe security bulletin. Review file access controls and implement proper path validation to prevent directory traversal.

Recommended fix High confidence

Latest stable 2.4.8 (e.g., 2.4.8) or latest patch for your version line (e.g., 2.4.4-p12+, 2.4.5-p11+, 2.4.6-p9+, 2.4.7-p4+)

  1. 1. Identify your current Adobe Commerce/Magento version by checking the composer.json file or the admin panel.
  2. 2. For Adobe Commerce 2.4.4: Upgrade to 2.4.4-p12 or later.
  3. 3. For Adobe Commerce 2.4.5: Upgrade to 2.4.5-p11 or later.
  4. 4. For Adobe Commerce 2.4.6: Upgrade to 2.4.6-p9 or later.
  5. 5. For Adobe Commerce 2.4.7: Upgrade to 2.4.7-p4 or later.
  6. 6. For Adobe Commerce 2.4.8: Upgrade to 2.4.8 stable or later.
  7. 7. Run composer update to apply the changes.
  8. 8. Clear the Magento cache using bin/magento cache:clean.
Caveat Minor patch upgrades typically have low breaking change risk; however, always review release notes for deprecated features and PHP version requirements before upgrading.

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

Fix this in Commerce Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
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,992.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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