dbcve.org
CommerceApplication · Adobe

CVE-2023-22250

MEDIUM · 5.3 CVSS v3.1 Published 2023-03-27
Fix available
A fix is available. Upgrade to 2.4.4 or later.
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.4-p2 (and earlier) and 2.4.5-p1 (and earlier) are affected by an Improper Access Control vulnerability that could result in a Security feature bypass. An attacker could leverage this vulnerability to impact the availability of a user's minor feature. 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 · moderate confidence

Adobe Commerce versions 2.4.4-p2 and earlier, and 2.4.5-p1 and earlier contain an Improper Access Control vulnerability that allows a Security feature bypass. An attacker can exploit this without user interaction to impact the availability of a minor feature in the commerce platform.

MitigationApply the Adobe security patch or upgrade to a patched version of Adobe Commerce as specified in the official Adobe security bulletin. Verify that access controls are properly enforced post-update.

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.4.4= 2.4.4= 2.4.5
Magento Open SourceApplication
Affected:< 2.4.4= 2.4.4= 2.4.5

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. Identify the installed Adobe Commerce or Magento Open Source version
    Run the following command in your Magento root directory: php bin/magento --version or check the composer.json file for the 'version' field
    Affected if The version shown is 2.4.4-p2 or earlier, or 2.4.5-p1 or earlier, or any version less than 2.4.4, or exactly 2.4.4 or 2.4.5
  2. Confirm the product type
    Check whether you are running Adobe Commerce (paid) or Magento Open Source (free) by reviewing your license file or composer package name: composer show magento/product-community-edition or magento/enterprise-edition
    Affected if The product is Adobe Commerce or Magento Open Source and the version falls within the affected ranges
  3. Verify if the access control feature is in use
    Review your store configuration to determine if the affected feature (related to security access controls) is enabled. Check Admin panel configuration settings or XML configuration files in app/etc/config.php for module status
    Affected if The vulnerable access control module is enabled and the installed version is within the affected version range

You are affected if your installed Adobe Commerce or Magento Open Source version is 2.4.4-p2 or earlier, or 2.4.5-p1 or earlier, or matches < 2.4.4, = 2.4.4, or = 2.4.5, and the affected access control feature is enabled.

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
Upgrade available Upgrade to 2.4.4 or later
Fixed in 2.4.4
Interim mitigation

Apply the Adobe security patch or upgrade to a patched version of Adobe Commerce as specified in the official Adobe security bulletin. Verify that access controls are properly enforced post-update.

Recommended fix High confidence

Adobe Commerce 2.4.6 or Magento Open Source 2.4.6 (or latest patch: 2.4.4-p3+ / 2.4.5-p2+)

  1. 1. Review current Adobe Commerce or Magento Open Source version using bin/magento --version or admin panel footer
  2. 2. For Adobe Commerce 2.4.4-p2 (or earlier): Apply patch AC-2.4.4-p3 or upgrade to 2.4.4-p3 or later
  3. 3. For Adobe Commerce 2.4.5-p1 (or earlier): Apply patch AC-2.4.5-p2 or upgrade to 2.4.5-p2 or later
  4. 4. Alternatively, upgrade to Adobe Commerce 2.4.6 or Magento Open Source 2.4.6 which contains the security fix
  5. 5. After applying patch or upgrade, clear Magento cache: bin/magento cache:flush
  6. 6. Verify the upgrade was successful by checking the version and testing critical user flows
Caveat Review Adobe Commerce 2.4.6 release notes for any breaking changes; patches typically contain only security fixes with no breaking changes

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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