CVE-2025-42946
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 · uneditedDue to directory traversal vulnerability in SAP S/4HANA (Bank Communication Management), an attacker with high privileges and access to a specific transaction and method in Bank Communication Management could gain unauthorized access to sensitive operating system files. This could allow the attacker to potentially read or delete these files hence causing a high impact on confidentiality and low impact on integrity. There is no impact on availability of the 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 confidenceDirectory traversal vulnerability in SAP S/4HANA Bank Communication Management allows authenticated attackers with high privileges and access to specific transactions to traverse file system paths and gain unauthorized read/delete access to sensitive operating system files. This results in high confidentiality impact but low integrity impact with no availability impact.
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
- Adjacent
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm SAP S/4HANA installationExecute transaction code SM37 or use SAP MII version checker to identify the SAP S/4HANA system version and confirm it is installed.Affected if The system is running SAP S/4HANA and the version falls within the affected range.
-
Identify Bank Communication Management moduleAccess SAP menu and navigate to Finance -> Bank Communication Management, or execute transaction code FQM to verify the BCM module is present and active in the system.Affected if The Bank Communication Management module is installed and enabled in the SAP S/4HANA environment.
-
Verify access to BCM transactionsExecute transaction codes associated with Bank Communication Management (such as FQ1, FQ2, or related BCM transaction codes) and verify whether the current user session can access these transaction entry points.Affected if The user has access to Bank Communication Management transactions in the SAP system.
-
Check user privilege levelUsing transaction SU01 or SUIM, review the current user's profile and assigned roles to determine if high-privilege access (such as SAP_ALL, SAP_NEW, or administrative BCM roles) is granted.Affected if The authenticated user possesses high-privilege SAP roles or administrative access to BCM functions.
-
Review file system access logsExamine SAP system traces (transaction ST03N), audit logs (transaction SM18/SM19), and operating system audit logs for any suspicious directory traversal patterns or unauthorized file read/delete operations targeting sensitive OS paths.Affected if Log entries indicate directory traversal attempts or unauthorized file access through BCM transactions.
A user is affected if they run SAP S/4HANA with Bank Communication Management enabled, have high-privilege access, and can execute the vulnerable BCM transactions that permit directory traversal to sensitive OS files.
Generated from the published advisory. Verify against your own configuration.
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 dataApply SAP security patches for this vulnerability and review/restrict access to the affected Bank Communication Management transactions and methods to only necessary high-privilege users.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-42946 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-42946 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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