dbcve.org
CommerceApplication · Adobe

CVE-2024-20759

HIGH · 8.1 CVSS v3.1 Published 2024-04-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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.6-p4, 2.4.5-p6, 2.4.4-p7, 2.4.7-beta3 and earlier are affected by a stored Cross-Site Scripting (XSS) vulnerability that could be abused by a high-privileged attacker to inject malicious scripts into vulnerable form fields. Malicious JavaScript may be executed in a victim’s browser when they browse to the page containing the vulnerable field. Confidentiality and integrity are considered high due to having admin impact.

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

Stored Cross-Site Scripting (XSS) vulnerability in Adobe Commerce (Magento) affecting multiple versions. A high-privileged admin user can inject malicious JavaScript into vulnerable form fields, which executes in other administrators' browsers when viewing the affected pages, potentially allowing session hijacking or privilege escalation.

MitigationApply vendor-supplied security patches or update to the fixed versions (2.4.6-p5, 2.4.5-p7, 2.4.4-p8, or 2.4.7 and later). Input validation and output encoding should be implemented on all admin-facing form fields.

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:all versions= 2.3.7= 2.4.0= 2.4.1= 2.4.2= 2.4.3= 2.4.4= 2.4.5= 2.4.6= 2.4.7
MagentoCMS
Affected:= 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. Determine your Adobe Commerce or Magento installed version
    Run the command 'php bin/magento --version' from the Magento root directory, or log into the admin panel and check the footer for the version number
    Affected if The version matches any of the affected versions: 2.3.7, 2.4.0, 2.4.1, 2.4.2, 2.4.3, 2.4.4, 2.4.5, 2.4.6, or 2.4.7, or shows as 'all versions' for Adobe Commerce
  2. Verify if you are running a patched or fixed version
    Compare your installed version against the fixed releases: 2.4.6-p5, 2.4.5-p7, 2.4.4-p8, or 2.4.7 and later. If your version is lower or you are on the base releases listed above without the -pN patch suffix, you are likely affected
    Affected if Your version is lower than the fixed versions listed above or does not have the required patch level
  3. Confirm admin panel accessibility
    Check if your Magento admin panel is exposed to the internet or accessible by untrusted users. Review your web server access controls and firewall rules for /admin or custom admin path endpoints
    Affected if The admin panel is accessible to users who are not fully trusted or is internet-facing without strong authentication controls
  4. Identify high-privileged admin accounts
    Review your admin user list in the Magento admin panel under System > Permissions > All Users, or query the admin_user table in the database, to determine which users have elevated privileges
    Affected if You have multiple admin users with high privileges, as the vulnerability requires a high-privileged admin user to inject the malicious script

You are affected if your installed Adobe Commerce or Magento version is 2.3.7 through 2.4.7 without the security patches applied, and you have high-privileged admin users who could inadvertently or maliciously inject XSS payloads into admin form fields.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied security patches or update to the fixed versions (2.4.6-p5, 2.4.5-p7, 2.4.4-p8, or 2.4.7 and later). Input validation and output encoding should be implemented on all admin-facing form fields.

Recommended fix High confidence

Upgrade to Adobe Commerce 2.4.6-p4 (or later), 2.4.5-p6 (or later), or 2.4.4-p7 (or later) depending on your version branch

  1. 1. Identify your current Adobe Commerce/Magento version in the admin panel under System > Web Setup Wizard or by checking the composer.json file
  2. 2. Determine which patch version applies to your current installation (2.4.4-p7, 2.4.5-p6, or 2.4.6-p4)
  3. 3. Back up your Adobe Commerce/Magento database and filesystem before applying any updates
  4. 4. For Adobe Commerce merchants: apply the appropriate security patch via the Quality Patches Tool (composer require magento/quality-patches) or apply the complete patch file from Adobe's security bulletin
  5. 5. For Magento Open Source users: apply the corresponding patch or upgrade to the patched version
  6. 6. Clear Magento cache after patching: bin/magento cache:clean
  7. 7. Verify the patch was applied successfully and test that the XSS vulnerability is no longer exploitable in affected form fields
  8. 8. Re-index the catalog if necessary: bin/magento indexer:reindex
Caveat Minor patches are backward-compatible; however, test in a staging environment before production deployment to ensure no customizations or third-party extensions are affected

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
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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