dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2024-39597

HIGH · 7.2 CVSS v3.1 Published 2024-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
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
In SAP Commerce, a user can misuse the forgotten password functionality to gain access to a Composable Storefront B2B site for which early login and registration is activated, without requiring the merchant to approve the account beforehand. If the site is not configured as isolated site, this can also grant access to other non-isolated early login sites, even if registration is not enabled for those other sites.

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

In SAP Commerce, the forgotten password functionality fails to enforce merchant approval requirements for B2B Composable Storefront sites with early login enabled. An attacker can bypass the account approval workflow by initiating a password reset, gaining unauthorized access without merchant review. Sites not configured as isolated also risk lateral access to other non-isolated early login sites.

MitigationConfigure B2B sites as isolated and ensure merchant approval workflows are enforced before password reset tokens become valid; review and restrict early login settings to only approved user populations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/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 SAP Commerce installation and version
    Locate SAP Commerce installation directory and check version file (manifest.xml, version.info, or via admin console). Compare installed version against SAP Commerce Cloud releases.
    Affected if Running SAP Commerce with B2B Composable Storefront component
  2. Confirm B2B Composable Storefront is in use
    Inspect the storefront configuration files (ycommercewebservices extension config, app configuration JSON) or check the storefront deployment for B2B-specific modules and composable storefront setup.
    Affected if B2B Composable Storefront is deployed and active
  3. Verify early login feature is enabled
    Check storefront or backend configuration for 'early login' or 'login.early.enabled' setting. Inspect the OCC layer configuration, property files (local.properties, extension specific configs), or B2B extension configuration.
    Affected if Early login is enabled in the configuration (value set to true)
  4. Check site isolation configuration
    Review B2B site configuration in Backoffice or via impex for 'isolated' or 'siteIsolation' attribute. Inspect the site configuration XML or database entries for B2B site isolation settings.
    Affected if B2B sites are NOT configured as isolated (isolated=false or not set)
  5. Examine merchant approval workflow enforcement
    Review the password reset flow and verify that merchant approval status is checked before allowing password change. Inspect the B2B approval workflow configuration and trace the forgotten password endpoint logic.
    Affected if Merchant approval is not enforced during password reset (approval status not validated in reset flow)

Environment is affected if running SAP Commerce with B2B Composable Storefront where early login is enabled and B2B sites are not isolated, allowing password reset to bypass merchant approval checks.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Configure B2B sites as isolated and ensure merchant approval workflows are enforced before password reset tokens become valid; review and restrict early login settings to only approved user populations.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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