dbcve.org
CommerceApplication · Adobe

CVE-2024-45117

HIGH · 7.6 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 →
82/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-p2, 2.4.6-p7, 2.4.5-p9, 2.4.4-p10 and earlier are affected by an Improper Input Validation vulnerability that could lead to arbitrary file system read. An admin attacker could exploit this vulnerability to read files from the system outside of the intended directories via PHP filter chain and also can have a low-availability impact on the service. 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

Improper input validation in Adobe Commerce allows authenticated admin users to read arbitrary files from the server filesystem via PHP filter chains, potentially exposing sensitive system files outside the web root.

MitigationApply the relevant security patch (Adobe Commerce security bulletin) or upgrade to a patched version (2.4.7-p3, 2.4.6-p8, 2.4.5-p10, or 2.4.4-p11 or later).

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L

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 Adobe Commerce or Magento installation and version
    Run 'bin/magento --version' from the web root, or check composer.json for the 'magento/product-commerce' or 'magento/product-community-edition' version, or inspect vendor/magento/framework/Version.php
    Affected if The installed version matches any version listed in the affected products (all versions for Adobe Commerce and Magento, or specific versions 2.3.7, 2.4.0-2.4.7, or B2b versions 1.3.3-1.3.5, 1.4.2)
  2. Confirm admin interface is accessible
    Verify the admin panel URL is reachable (typically /admin or /backend) and that network or firewall rules do not restrict access to internal users only
    Affected if The admin panel is internet-facing or accessible to untrusted users, creating a path for authenticated attacks
  3. Audit existing admin user accounts
    Query the admin_user table in the database to list all admin accounts, or use 'bin/magento admin:user:list' to identify active admin accounts
    Affected if Any active admin user accounts exist in the system, as the vulnerability requires authenticated admin access to exploit

You are affected if Adobe Commerce or Magento is installed with a version matching the affected ranges and any admin user account exists in the system.

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 the relevant security patch (Adobe Commerce security bulletin) or upgrade to a patched version (2.4.7-p3, 2.4.6-p8, 2.4.5-p10, or 2.4.4-p11 or later).

Recommended fix High confidence

Upgrade to Adobe Commerce 2.4.7-p3 or later (or the latest patched version for your release line: 2.4.6-p8+, 2.4.5-p10+, 2.4.4-p11+)

  1. 1. Identify the current Adobe Commerce/Magento version installed using the admin panel (System > Configuration > Advanced > Admin > Advanced > Disable Modules Output, or check composer.json)
  2. 2. Review the Adobe Security Bulletin (helpx.adobe.com) for the complete list of fixed versions corresponding to your release line
  3. 3. Plan the upgrade following Adobe's upgrade documentation: https://experienceleague.adobe.com/docs/commerce-operations/upgrade-guide/overview.html
  4. 4. Create a full backup of the database and codebase before upgrading
  5. 5. Test the upgrade in a staging environment before applying to production
  6. 6. Apply the upgrade to the latest patched version (e.g., 2.4.7-p3 or later for the 2.4.7 line, or the latest available secure version for your release line)
  7. 7. Verify the fix by checking that the vulnerable code paths are no longer accessible and confirm the version number post-upgrade
  8. 8. Monitor system logs for any anomalous file access attempts
Caveat Upgrading between major versions may require compatibility testing of custom modules, theme changes, and potential data migration efforts; review Adobe's compatibility matrix 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
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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