dbcve.org
Insufficiently Protected CredentialsWeakness · CWE-522

CVE-2025-42897

MEDIUM · 5.3 CVSS v3.1 Published 2025-11-11
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
Due to information disclosure vulnerability in anonymous API provided by SAP Business One (SLD), an attacker with normal user access could gain access to unauthorized information. As a result, it has a low impact on the confidentiality of the application but no impact on the integrity and availability.

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

Information disclosure vulnerability in the anonymous API of SAP Business One's System Landscape Directory (SLD) allows authenticated users with normal privileges to access information they are not authorized to view. The vulnerability stems from insufficient access controls on certain API endpoints.

MitigationRestrict or disable the anonymous API endpoints in SLD, implement proper authorization checks, and apply any available SAP security patches for Business One. Verify user permissions before returning sensitive data.

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
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. Confirm SAP Business One SLD component is installed
    Locate the System Landscape Directory installation directory (typically under the SAP Business One setup path) or check the SAP Business One system information via SAP Business One Client -> Help -> System Information. Verify the SLD service is running by checking Windows Services or via SAP B1iXpress console.
    Affected if SLD component is present and running in the environment
  2. Determine if anonymous API endpoints are enabled
    Access the SLD configuration interface (typically via https://<server>:4000/sld or the SLD administration console). Navigate to the API settings or anonymous access configuration section. Check whether anonymous or public API access is permitted for the SLD endpoints.
    Affected if Anonymous or unauthenticated API access is enabled in SLD configuration
  3. Review user role assignments in SLD
    In the SAP Business One SLD administration panel, examine the user roles and privileges assigned to standard (non-administrator) users. Check if normal privileged users have access to system landscape, license, or component information that should be restricted.
    Affected if Standard users with normal privileges are defined in the SLD user management
  4. Inspect API endpoint access control configuration
    Examine the SLD API configuration files (typically found in the SLD installation directory under config or webapps/sld.war). Look for XML or properties files defining API authorization rules. Verify whether sensitive endpoints lack proper role-based access control (RBAC) enforcement.
    Affected if API endpoints do not enforce role-based authorization or allow normal users to access administrative data
  5. Check for sensitive data exposure via API responses
    Using a standard (non-admin) user account, make API calls to SLD endpoints such as /sld/api/v1/systems, /sld/api/v1/licenses, or /sld/api/v1/landscape. Compare the returned data against what that user should legitimately access according to authorization policies.
    Affected if Normal privileged users can retrieve information about system configurations, license details, or other users that they should not be authorized to view

A user is affected if the SAP Business One SLD anonymous API is enabled and standard (non-administrator) users can access sensitive system, license, or landscape information beyond their authorized scope.

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

Restrict or disable the anonymous API endpoints in SLD, implement proper authorization checks, and apply any available SAP security patches for Business One. Verify user permissions before returning sensitive data.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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