dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2025-42951

HIGH · 8.8 CVSS v3.1 Published 2025-08-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 broken authorization, SAP Business One (SLD) allows an authenticated attacker to gain administrator privileges of a database by invoking the corresponding API.�As a result , it has a high impact on the confidentiality, integrity, and availability of the application.

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

SAP Business One's System Landscape Directory (SLD) contains a broken authorization vulnerability that allows an authenticated attacker to invoke a specific API and escalate privileges to gain database administrator access. This privilege escalation compromises the confidentiality, integrity, and availability of the application and its data.

MitigationApply the official SAP security patch for CVE-2025-42951 and verify that SLD API access controls properly enforce authorization boundaries to prevent privilege escalation.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 if SLD is deployed
    Locate the SAP Business One System Landscape Directory installation. Check for SLD service/process running, or look for SLD configuration files in the SAP Business One installation directory (typically under /system-landscape-directory or /sld). Consult SAP transaction code SLDCHECK or equivalent if accessible.
    Affected if SLD is installed and running in the environment
  2. Verify SLD API accessibility
    Identify the SLD API endpoints (commonly under /sld/ or /SLD/ path). Use network scanning or check SAP configuration files (like sld-config.xml) to list exposed API endpoints. Attempt to access the specific API path used for privilege escalation if identifiable through logs or documentation.
    Affected if SLD API endpoints are exposed and accessible to network users
  3. Check authentication configuration
    Review SLD authentication settings in the configuration files (e.g., sld.cfg, web.xml, or SAP-specific config). Determine if anonymous access is allowed or if API calls require valid authentication.
    Affected if The vulnerable API accepts authenticated requests without proper authorization validation
  4. Audit SLD user roles and permissions
    Access the SLD administration console or user management interface. List all users and their assigned roles. Look for any unexpected role assignments, especially roles with elevated privileges or administrative access that were not intentionally granted.
    Affected if Users possess roles or permissions that grant administrative database access beyond their intended scope
  5. Review API access logs for escalation attempts
    Examine SLD server logs (typically in /logs/ or /trace/ directories) for API calls that may indicate privilege escalation attempts. Search for commands or API invocations that modify user roles, create administrator accounts, or grant elevated permissions.
    Affected if Logs show API calls resulting in unauthorized privilege escalation or unexpected administrative account creation

The environment is affected if SAP Business One SLD is deployed and the vulnerable API permits authenticated users to escalate privileges to administrative database access without proper authorization 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

Apply the official SAP security patch for CVE-2025-42951 and verify that SLD API access controls properly enforce authorization boundaries to prevent privilege escalation.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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