dbcve.org
CommerceApplication · Adobe

CVE-2023-38251

MEDIUM · 5.3 CVSS v3.1 Published 2023-10-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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-beta1 (and earlier), 2.4.6-p2 (and earlier), 2.4.5-p4 (and earlier) and 2.4.4-p5 (and earlier) are affected by a Uncontrolled Resource Consumption vulnerability that could lead in minor application denial-of-service. 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 versions prior to 2.4.7-beta1, 2.4.6-p2, 2.4.5-p4, and 2.4.4-p5 contain an uncontrolled resource consumption vulnerability that allows attackers to cause a minor denial-of-service condition without any user interaction, likely through repeated requests that exhaust server resources.

MitigationApply the vendor security patches for the affected Adobe Commerce versions or upgrade to a patched release to remediate this uncontrolled resource consumption vulnerability.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Check Adobe Commerce version via CLI
    Run 'bin/magento --version' or 'php bin/magento --version' from the Magento root directory
    Affected if The output shows version 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
  2. Check Adobe Commerce version in composer.json
    Open composer.json in the Magento root directory and locate the 'version' field under the 'extra' section or check the installed.php file in vendor/composer/
    Affected if The version field matches any of: 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
  3. Check Adobe Magento version in admin panel
    Log into the admin panel and scroll to the footer of any page; the version is displayed there
    Affected if The displayed version is 2.4.4, 2.4.5, 2.4.6, or 2.4.7 (Magento edition)
  4. Verify patch installation status
    Check the app/etc/patches.status file or examine composer.lock for installed security patch packages (such as patch-12345)
    Affected if No security patches for CVE-2023-38251 are installed, and the base version remains in the affected range

You are affected if your installed Adobe Commerce or Magento version is 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 and no corresponding security patch has 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 security patches for the affected Adobe Commerce versions or upgrade to a patched release to remediate this uncontrolled resource consumption vulnerability.

Recommended fix High confidence

Adobe Commerce 2.4.7 (stable release) or latest available patch for your branch (2.4.4-p6+, 2.4.5-p5+, 2.4.6-p3+)

  1. 1. Review the Adobe Commerce Security Bulletin (Adobe KB) for CVE-2023-38251 for complete details
  2. 2. Back up your Adobe Commerce/Magento installation and database before proceeding
  3. 3. If running a version prior to 2.4.4, first upgrade to a supported version (2.4.4 or later)
  4. 4. For version 2.4.4: Upgrade to 2.4.4-p6 or later (composer require magento/product-community-edition 2.4.4-p6 --no-update)
  5. 5. For version 2.4.5: Upgrade to 2.4.5-p5 or later
  6. 6. For version 2.4.6: Upgrade to 2.4.6-p3 or later
  7. 7. For version 2.4.7-beta1: Upgrade to 2.4.7 (stable release)
  8. 8. Run composer update to apply changes
Caveat Standard Adobe Commerce upgrade risks apply - test in staging environment before production deployment; review compatibility with custom extensions and third-party modules

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Commerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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