dbcve.org
CommerceApplication · Adobe

CVE-2023-29287

MEDIUM · 5.3 CVSS v3.1 Published 2023-06-15
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.6 (and earlier), 2.4.5-p2 (and earlier) and 2.4.4-p3 (and earlier) are affected by an Information Exposure vulnerability that could lead to a security feature bypass. An attacker could leverage this vulnerability to leak minor user data. 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.6 and earlier, 2.4.5-p2 and earlier, and 2.4.4-p3 and earlier contain an information exposure vulnerability that allows attackers to bypass security features and leak minor user data without any user interaction.

MitigationApply the vendor security patch or upgrade to a patched version of Adobe Commerce (2.4.6-p1, 2.4.5-p3, or 2.4.4-p4 or later) following standard deployment procedures including staging verification and full functionality testing.

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
MagentoCMS
Affected:= 2.4.4= 2.4.5= 2.4.6

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 installed Adobe Commerce or Magento version
    Check the composer.json file in the Magento root directory for the 'version' field, or run 'composer show magento/framework' to display the installed version.
    Affected if The installed version matches 2.4.6, 2.4.5-p2 or earlier, 2.4.4-p3 or earlier, or any 2.3.7 through 2.4.0 through 2.4.3 installation.
  2. Confirm product type is Adobe Commerce
    Review the composer.json 'name' field - Adobe Commerce installations typically show 'magento/project-enterprise-edition' while open source shows 'magento/project-community-edition'.
    Affected if The product is Adobe Commerce (enterprise edition) and the version falls within the affected range.
  3. Verify the patch state of the installation
    Check if security patch SUPEE-10888 or the specific Adobe security patch for CVE-2023-29287 has been applied by reviewing the app/etc/applied.patches.list file.
    Affected if The applied.patches.list file does not contain the CVE-2023-29287 patch or equivalent security patch, and the base version is in the affected range.
  4. Check for public-facing API or user data endpoints
    Review the storefront and API configurations to determine if endpoints that could leak user data are exposed, particularly those related to customer accounts or order information.
    Affected if The system exposes public endpoints that could potentially leak user data without authentication.

A user is affected if their Adobe Commerce or Magento installation version is 2.4.6 or earlier (specifically 2.4.5-p2 and earlier, 2.4.4-p3 and earlier, or 2.3.7 through 2.4.3) and the CVE-2023-29287 security patch has 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 security patch or upgrade to a patched version of Adobe Commerce (2.4.6-p1, 2.4.5-p3, or 2.4.4-p4 or later) following standard deployment procedures including staging verification and full functionality testing.

Recommended fix High confidence

Adobe Commerce/Magento 2.4.7 (or latest 2.4.x release)

  1. Identify your current Adobe Commerce or Magento version using the admin panel or command line (bin/magento --version)
  2. If running Commerce 2.3.7, 2.4.0, 2.4.1, or 2.4.2: upgrade to Adobe Commerce 2.4.7 or later
  3. If running Magento 2.4.4 with patch level below p4: upgrade to at least 2.4.4-p4
  4. If running Magento 2.4.5 with patch level below p3: upgrade to at least 2.4.5-p3
  5. If running Magento 2.4.6 or earlier: upgrade to Adobe Commerce/Magento 2.4.7
  6. Before upgrading, create a full backup of the codebase, database, and media files
  7. Run composer require with the target version, e.g., composer require magento/product-community-edition=2.4.7 --no-update
  8. Run composer update to install the new packages
Caveat Review Adobe's release notes for 2.4.7 for potential breaking changes; major version upgrade from 2.3.x to 2.4.x may require theme and extension compatibility review

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
  • Testing4.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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