dbcve.org
Business ConnectorApplication · Sap

CVE-2025-42894

MEDIUM · 6.8 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 →
70/100
Remediation priority · Elevated
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 a Path Traversal vulnerability in SAP Business Connector, an attacker authenticated as an administrator with adjacent access could read, write, overwrite, and delete arbitrary files on the host system. Successful exploitation could enable the attacker to execute arbitrary operating system commands on the server, resulting in a complete compromise of the confidentiality, integrity, and availability of the affected system.

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 · high confidence

A path traversal vulnerability in SAP Business Connector allows an authenticated administrator with adjacent network access to read, write, overwrite, and delete arbitrary files on the host filesystem. Successful exploitation enables arbitrary OS command execution, leading to complete system compromise.

MitigationApply the vendor security patch for SAP Business Connector immediately. Until patched, restrict administrative access to trusted personnel only and monitor for suspicious file operations on the host system.

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
Business ConnectorApplication
Affected:= 4.8

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

CVSS:3.1/AV:A/AC:L/PR:H/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. Confirm SAP Business Connector installation
    Identify if SAP Business Connector software is installed on the system by checking for its typical installation directories or running processes related to SAP BC.
    Affected if SAP Business Connector is present on the system
  2. Verify the installed version
    Determine the exact version of SAP Business Connector installed. Check version files,About dialogs, or use SAP BC administration tools to retrieve the version number.
    Affected if The installed version is exactly 4.8 (the only affected version listed)
  3. Confirm administrator access is available
    Verify whether the SAP Business Connector administrator interface (typically web-based or remoting service) is accessible on adjacent networks or remotely.
    Affected if The administrator interface is exposed to adjacent or untrusted networks with administrator credentials in use
  4. Inspect for suspicious file system activity
    Review host filesystem logs and file access records for unusual read, write, or delete operations in system directories outside the SAP BC working directories.
    Affected if File operations are observed outside expected SAP Business Connector paths, particularly in system directories
  5. Check for unauthorized admin accounts
    Audit SAP Business Connector user accounts and administrator accounts for any unexpected or unauthorized entries.
    Affected if Unknown or unexpected administrator accounts exist in the SAP BC user database

A system is affected if it runs SAP Business Connector version 4.8 with an exposed administrator interface accessible from adjacent networks.

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 for SAP Business Connector immediately. Until patched, restrict administrative access to trusted personnel only and monitor for suspicious file operations on the host system.

Recommended fix Moderate confidence

Latest SAP Business Connector version beyond 4.8 (consult SAP Security Note for exact fixed release)

  1. 1. Verify the currently installed SAP Business Connector version by accessing the SAP Business Connector administration interface or checking the installed software inventory.
  2. 2. Review the SAP Business Connector 4.8 release notes and any available SAP Security Notes related to CVE-2025-42894 for specific upgrade requirements.
  3. 3. Schedule a maintenance window for the upgrade procedure.
  4. 4. Perform a complete backup of the current SAP Business Connector configuration, adapters, and any custom developed integrations.
  5. 5. Upgrade SAP Business Connector to the latest available version that addresses CVE-2025-42894 - typically this would be a version higher than 4.8 (consult SAP Support Portal at support.sap.com for the exact fixed version).
  6. 6. After upgrade, verify the path traversal vulnerability is remediated by reviewing the security configuration settings and ensuring file access controls are properly enforced.
  7. 7. Validate that all existing integrations and trading partner configurations function correctly after the upgrade.
Caveat Review SAP release notes for potential compatibility changes between version 4.8 and the target upgrade version - custom adapters or integrations may require updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Business Connector Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,320
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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