dbcve.org
CommerceApplication · Adobe

CVE-2024-45118

MEDIUM · 6.5 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 →
71/100
Remediation priority · Elevated
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 Access Control vulnerability that could result in a Security feature bypass. A low-privileged attacker could leverage this vulnerability to bypass security measures and have high impact on integrity. 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 · high confidence

Adobe Commerce contains an Improper Access Control vulnerability allowing low-privileged attackers to bypass security measures. The flaw affects versions 2.4.7-p2, 2.4.6-p7, 2.4.5-p9, 2.4.4-p10 and earlier, with high integrity impact and no user interaction required for exploitation.

MitigationApply the vendor-released security patches for Adobe Commerce to address the access control bypass, or upgrade to the latest patched version.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 Adobe Commerce or Magento installed version
    Locate the version file or use admin panel to check the current installation version. Common locations include composer.json in the root directory or the admin panel under System > Configuration > Advanced > Advanced (for Magento 1.x) or System > Settings (for Magento 2.x)
    Affected if The installed version is 2.4.4-p10 or earlier, 2.4.5-p9 or earlier, 2.4.6-p7 or earlier, 2.4.7-p2 or earlier, or any version matching 2.3.7, 2.4.0, 2.4.1, 2.4.2, or 2.4.3 through 2.4.7 without the indicated patch versions
  2. Check if Adobe Commerce B2B module is installed
    Use the command line bin/magento module:status or inspect the composer.json file to see if the Adobe Commerce B2B module is present in the installation
    Affected if The B2B module is installed and its version is 1.3.3, 1.3.4, 1.3.5, or 1.4.2
  3. Verify current security patch level
    Review the applied patches or cumulative patches installed on the system. Check the /vendor/magento/patch-info or similar patch documentation if available
    Affected if Security patches for this CVE have not been applied and the version falls within the affected ranges listed above

The environment is affected if Adobe Commerce or Magento is installed at any of the listed affected versions and the vendor security patches for this CVE have not been applied.

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 vendor-released security patches for Adobe Commerce to address the access control bypass, or upgrade to the latest patched version.

Recommended fix High confidence

Adobe Commerce 2.4.7-p3 or later (or latest 2.4.7.x); for older branches: 2.4.6-p8+, 2.4.5-p10+, 2.4.4-p11+

  1. 1. Identify your current Adobe Commerce/Magento version by running: php bin/magento --version
  2. 2. Review the Adobe Security Bulletin (Adobe Tech Note) for CVE-2024-45118 at helpx.adobe.com for complete remediation details
  3. 3. Create a full backup of your codebase, database, and media files before proceeding
  4. 4. Upgrade Adobe Commerce to version 2.4.7-p3 or later (or the latest 2.4.7.x release)
  5. 5. If running 2.4.6.x, upgrade to 2.4.6-p8 or later
  6. 6. If running 2.4.5.x, upgrade to 2.4.5-p10 or later
  7. 7. If running 2.4.4.x, upgrade to 2.4.4-p11 or later
  8. 8. After upgrade, clear caches: php bin/magento cache:flush
Caveat Standard patch upgrades typically have minimal breaking changes; test thoroughly in staging before production deployment

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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