dbcve.org
CommerceApplication · Adobe

CVE-2024-45116

HIGH · 8.1 CVSS v3.1 Published 2024-10-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.7-p2, 2.4.6-p7, 2.4.5-p9, 2.4.4-p10 and earlier are affected by a Cross-Site Scripting (XSS) vulnerability that could be exploited to execute arbitrary code. If an admin attacker can trick a user into clicking a specially crafted link or submitting a form, malicious scripts may be executed within the context of the victim's browser and have high impact on confidentiality and integrity. Exploitation of this issue requires 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 · high confidence

A Cross-Site Scripting (XSS) vulnerability in Adobe Commerce allows an authenticated admin attacker to inject malicious scripts through specially crafted links or forms. When victim users interact with these, the scripts execute within their browser context, enabling session hijacking, data theft, or privilege escalation.

MitigationApply Adobe's official security patch for this CVE and upgrade to a supported version. Implement Content Security Policy (CSP) headers as defense-in-depth to mitigate XSS execution.

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
Commerce B2bApplication
Affected:= 1.3.3= 1.3.4= 1.3.5= 1.4.2
MagentoCMS
Affected:all versions= 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 your Adobe Commerce or Magento installation version
    Log into the admin panel and navigate to System > Settings > Advanced > Admin > Admin User Model or check the composer.json file in the installation root for the version entry
    Affected if The installed version matches any of the affected versions listed (2.3.7, 2.4.0 through 2.4.7 for Commerce; 2.3.7, 2.4.3 through 2.4.7 for Magento; or any version if 'all versions' applies)
  2. Verify if the B2B extension version is affected
    If Adobe Commerce B2B is installed, check the B2B extension version through composer or the admin panel under Stores > Configuration > B2B Features
    Affected if The B2B extension version is 1.3.3, 1.3.4, 1.3.5, or 1.4.2
  3. Confirm admin panel access exists
    Verify that the admin panel is accessible and that administrator accounts exist. This vulnerability requires an authenticated admin attacker to inject the malicious script
    Affected if The admin panel is reachable and active user accounts with admin privileges exist in the system
  4. Review recent admin account activity
    Check the admin user logs or audit trails for any unexpected admin accounts created or unusual modifications, especially around the time frame of this vulnerability disclosure
    Affected if Unexpected admin accounts or suspicious admin activity is found in the logs
  5. Inspect for unfamiliar admin-created content
    Review CMS pages, blocks, and widgets created by administrators for any suspicious JavaScript or iframe elements that were not intentionally added
    Affected if Malicious script tags or unexpected external resource references are found in admin-created content

Your environment is likely affected if you run any Adobe Commerce, Magento, or B2B version matching the listed affected versions and your admin panel is accessible to authenticated users.

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 Adobe's official security patch for this CVE and upgrade to a supported version. Implement Content Security Policy (CSP) headers as defense-in-depth to mitigate XSS execution.

Recommended fix High confidence

Upgrade to Adobe Commerce 2.4.7-p3 / 2.4.6-p8 / 2.4.5-p10 / 2.4.4-p11 or later (or latest 2.4.x/2.3.x compatible release with security patch)

  1. Identify current Adobe Commerce/Magento version in use (check admin panel or composer.json)
  2. Review the Adobe Commerce release calendar or helpx.adobe.com for the security patch release containing the fix for CVE-2024-45116
  3. Plan upgrade to the minimum patched version: for 2.4.4.x upgrade to 2.4.4-p11 or later; for 2.4.5.x upgrade to 2.4.5-p10 or later; for 2.4.6.x upgrade to 2.4.6-p8 or later; for 2.4.7.x upgrade to 2.4.7-p3 or later
  4. Backup the entire Magento file system and database before upgrade
  5. Run composer require magento/product-community-edition:<fixed_version> --no-update to update version constraints
  6. Run composer update to fetch new packages
  7. Run bin/magento setup:upgrade to apply database migrations
  8. Clear caches with bin/magento cache:flush
Caveat Adobe Commerce patch upgrades are generally backward compatible; however, review release notes for any breaking changes in custom code compatibility or deprecated features before upgrading

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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