dbcve.org
CommerceApplication · Adobe

CVE-2024-39400

HIGH · 8.1 CVSS v3.1 Published 2024-08-14
Fix available
A fix is available. Upgrade to after 2.4.3 or later.
See remediation →
85/100
Remediation priority · High
Remotely reachable

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 a DOM-based Cross-Site Scripting (XSS) vulnerability. This vulnerability could allow an admin attacker to inject and execute arbitrary JavaScript code within the context of the user's browser session. Exploitation of this issue requires user interaction, such as convincing a victim to click on a malicious link. Confidentiality and integrity impact is high as it affects other admin accounts.

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 versions 2.4.4-p9 through 2.4.7-p1 contain a DOM-based Cross-Site Scripting (XSS) vulnerability allowing an authenticated admin attacker to inject malicious JavaScript through a specific endpoint that is reflected in the browser's DOM without proper sanitization. Successful exploitation enables session hijacking of other admin users who click the crafted malicious link.

MitigationApply the vendor-supplied security patch for CVE-2024-39400 which implements proper output encoding on the vulnerable parameter to prevent script injection. Verify no other similar DOM XSS vectors exist in admin-facing code.

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
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/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 installed Adobe Commerce or Magento version
    Run the CLI command 'php bin/magento --version' or check the composer.json file in the Magento root directory for the version attribute
    Affected if The installed version is 2.4.4, 2.4.5, 2.4.6, or 2.4.7 (including any patch versions within these releases) or is 2.4.3 or lower
  2. Confirm admin panel access is enabled
    Check the app/etc/env.php file for admin URL path and verify the admin panel is accessible over the network
    Affected if The admin panel is exposed and accessible to network attackers
  3. Locate the vulnerable endpoint parameter
    Review admin-facing controllers and templates for parameters that are reflected in the browser DOM without encoding. Examine response headers and HTML source for user-supplied input that is directly inserted into page output
    Affected if A parameter in an admin endpoint accepts user input and reflects it directly into the DOM without proper sanitization
  4. Verify patch application status
    Search the codebase for the security patch file or check if the specific fix for CVE-2024-39400 has been applied to the vulnerable template/controller file
    Affected if The patch has not been applied and the vulnerable endpoint parameter is found to be reflected without output encoding

You are affected if your Adobe Commerce or Magento installation runs version 2.4.4 through 2.4.7 and an unauthenticated or authenticated admin user can access an endpoint that reflects input into the DOM without output encoding.

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 patch for CVE-2024-39400 which implements proper output encoding on the vulnerable parameter to prevent script injection. Verify no other similar DOM XSS vectors exist in admin-facing code.

Recommended fix High confidence

Adobe Commerce 2.4.7-p1 (or minimum patched version per your branch: 2.4.4-p9, 2.4.5-p8, or 2.4.6-p6)

  1. 1. Identify your current Adobe Commerce/Magento version in the admin panel under System > Configuration > General > Advanced > Admin or by running: bin/magento --version
  2. 2. Determine the appropriate target version based on your current installation: if on <=2.4.3 or 2.4.4, upgrade to 2.4.7-p1 (recommended) or minimum 2.4.4-p9; if on 2.4.5, upgrade to minimum 2.4.5-p8; if on 2.4.6, upgrade to minimum 2.4.6-p6
  3. 3. Create a complete backup of the database and file system before upgrading
  4. 4. Put the store in maintenance mode: bin/magento maintenance:enable
  5. 5. Upgrade using Composer: composer require magento/product-community-edition=2.4.7-p1 --no-update, then composer update
  6. 6. Clear caches: bin/magento cache:flush
  7. 7. Run the upgrade scripts: bin/magento setup:upgrade
  8. 8. Recompile the di configuration if in production mode: bin/magento setup:di:compile
Caveat Magento 2.4.x patch upgrades typically have minimal breaking changes but review release notes for deprecations, especially if using custom themes or third-party extensions that may require updates for compatibility

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
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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