Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2025-27436 Overview
CVE-2025-27436 is a missing access control vulnerability in the Manage Bank Statements function of SAP S/4HANA. An authenticated attacker can delete attachments associated with a posted bank statement because the application fails to verify authorization at the resource level. The flaw is classified as Authorization Bypass Through User-Controlled Key [CWE-639]. Exploitation requires network access and low privileges, with no user interaction. The issue affects data integrity only, with no impact on confidentiality or availability.
Critical Impact
Authenticated users can delete bank statement attachments they are not authorized to modify, undermining the integrity of financial records in SAP S/4HANA.
Affected Products
- SAP S/4HANA (Manage Bank Statements application)
- Deployments exposing the Manage Bank Statements Fiori app to authenticated users
- Refer to SAP Note 3565835 for the authoritative version list
Discovery Timeline
- 2025-03-11 - CVE-2025-27436 published to the National Vulnerability Database (NVD)
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2025-27436
Vulnerability Analysis
The Manage Bank Statements component in SAP S/4HANA exposes resource endpoints that handle attachments attached to posted bank statements. The application accepts an authenticated request to delete an attachment but does not validate whether the requesting user is authorized to act on that specific resource. Any valid user session can therefore remove attachments linked to statements owned by other users or business units.
The weakness falls under [CWE-639] Authorization Bypass Through User-Controlled Key, commonly described as an Insecure Direct Object Reference. The server trusts the resource identifier passed by the client without binding it to the caller's permissions.
Because only deletion of attachments is possible, the impact is limited to integrity. Audit records, reconciliation evidence, and supporting documents stored with bank statements may be destroyed. Confidential statement data is not disclosed and the service continues to operate.
Root Cause
The root cause is a missing object-level authorization check in the attachment deletion handler. The code path validates the user session but omits the check that confirms the attachment belongs to a bank statement the user is allowed to maintain.
Attack Vector
The attack is executed over the network against the Fiori or OData endpoint that services bank statement attachments. An authenticated user issues a delete request referencing the target attachment identifier. The server performs the deletion without verifying ownership or role scope. No social engineering or client-side interaction is required.
No verified public proof-of-concept exploitation code is available. Review the SAP Note 3565835 for vendor technical details.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2025-27436
Indicators of Compromise
- Unexpected DELETE requests against the Manage Bank Statements attachment OData service from accounts without bank accounting roles.
- Audit log entries showing attachment removals on posted bank statements by users outside the Treasury or Finance organization.
- Gaps in attachment history for reconciled bank statements that were previously documented.
Detection Strategies
- Enable SAP Security Audit Log (SAL) events for attachment service calls and alert on DELETE operations by non-privileged users.
- Correlate HTTP access logs from the SAP Gateway with user role assignments to identify authorization anomalies.
- Baseline normal attachment activity per role and alert on deviations in volume or user population.
Monitoring Recommendations
- Forward SAP SAL, Gateway, and change document logs to a centralized SIEM for continuous review.
- Monitor the /sap/opu/odata/ endpoints that back the Manage Bank Statements app for anomalous verbs and parameter patterns.
- Review change documents for bank statement objects on a scheduled basis to confirm attachment integrity.
How to Mitigate CVE-2025-27436
Immediate Actions Required
- Apply the SAP security correction referenced in SAP Note 3565835 during the next available maintenance window.
- Restrict access to the Manage Bank Statements Fiori catalog to users with a documented business need.
- Review assigned roles and remove excess authorizations for the bank statement attachment service.
Patch Information
SAP released the fix as part of SAP Security Patch Day. Download and apply the correction described in SAP Note 3565835. Additional advisories are listed on the SAP Security Patch Day portal.
Workarounds
- Remove the Manage Bank Statements tile from catalogs of users who do not require it until the patch is deployed.
- Tighten role-based authorizations for the attachment service and enforce segregation of duties for Treasury functions.
- Enable detailed Security Audit Log coverage on attachment DELETE operations to detect misuse while the fix is pending.
# Configuration example
# Enable SAP Security Audit Log filter for attachment deletions
# via transaction SM19/RSAU_CONFIG:
# Event class: RFC/Web Service
# Audit class: Transaction / RFC
# Severity: Critical
# Filter: User = * Event = AU6 (deletion events)
# Activate the filter and reload the audit log via SM20/RSAU_READ_LOG.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

