Skip to main content
VulnerabilityPublished Updated

CVE-2025-42933: SAP Business One (SLD) · Insufficiently Protected Credentials

Affects SAP Business One (SLD)Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

  1. Apply official patches from SAP immediately once they become available to address the encryption enforcement flaw in the SLD backend service.
  2. Until patches are released, enforce network-level encryption such as VPNs or TLS tunnels to protect communications between SAP Business One clients and the SLD service.
  3. Restrict network access to the SLD service to trusted hosts and networks only, using firewalls and access control lists.
  4. Monitor network traffic for unusual or unauthorized access patterns to the SLD service, employing intrusion detection/prevention systems.
  5. Review and harden SAP Business One user privileges to minimize the impact of credential exposure.
  6. Conduct regular security audits and credential rotation policies to limit the window of opportunity for attackers.
  7. Educate administrators and users about the risks and signs of compromise related to SAP Business One credentials.
  8. Implement multi-factor authentication (MFA) where possible to reduce the risk of credential misuse.
  9. Maintain up-to-date backups of SAP Business One data to enable recovery in case of integrity or availability compromise.

Description

When a user logs in via SAP Business One native client, the SLD backend service fails to enforce proper encryption of certain APIs. This leads to exposure of sensitive credentials within http response body. As a result, it has a high impact on the confidentiality, integrity, and availability of the application.

References

Community reviews

Loading reviews…