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-42915 Overview
CVE-2025-42915 is a missing authorization vulnerability in the SAP Fiori application Manage Payment Blocks. The application fails to perform the authorization checks required to restrict sensitive functionality to specific user groups. An authenticated attacker with basic user privileges can abuse these functions to view and modify payment block data they should not be able to access.
The weakness is tracked as CWE-862: Missing Authorization. It affects both the confidentiality and integrity of the application but does not impact availability.
Critical Impact
Any authenticated SAP user can invoke privileged Manage Payment Blocks functions, enabling unauthorized read and modification of payment control data used in financial workflows.
Affected Products
- SAP Fiori application Manage Payment Blocks
- SAP S/4HANA environments that expose the affected Fiori app
- Deployments referenced in SAP Note #3409013
Discovery Timeline
- 2025-09-09 - CVE-2025-42915 published to the National Vulnerability Database (NVD) as part of SAP Security Patch Day
- 2026-06-17 - Last updated in NVD
Technical Details for CVE-2025-42915
Vulnerability Analysis
The Manage Payment Blocks Fiori application exposes functions that let users set, release, and modify payment blocks on supplier invoices and other financial documents. These actions should be restricted to specific authorization groups responsible for accounts payable control. The application does not enforce those authorization checks on all operations.
An attacker needs only a valid SAP account with basic privileges to reach the affected endpoints. Once authenticated, the attacker can trigger functionality that should be gated behind role-based restrictions. Because payment blocks directly influence whether invoices are paid, abuse affects financial integrity as well as confidentiality of related document data.
The attack is executed over the network against the Fiori frontend or the underlying OData service. No user interaction and no elevated privileges are required beyond standard authenticated access.
Root Cause
The root cause is a missing authorization check [CWE-862] in the backend logic that services the Fiori app. Authorization objects that should validate the caller's membership in the appropriate user group are not evaluated before the function executes. The application therefore trusts any authenticated session to invoke restricted operations.
Attack Vector
Exploitation requires network access to the SAP Fiori Launchpad or the OData service exposed by the application. The attacker authenticates with any valid SAP user account, navigates to the Manage Payment Blocks app or calls its OData endpoints directly, and issues requests that invoke restricted actions. The backend processes the request without verifying authorization, returning restricted data or applying unauthorized changes.
No verified public proof-of-concept is available at the time of writing. Technical specifics are restricted to customers with access to SAP Note #3409013.
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-42915
Indicators of Compromise
- OData requests to the Manage Payment Blocks service originating from user accounts outside the expected accounts-payable authorization groups.
- Unexpected changes to payment block indicators on vendor invoices, especially blocks being released by users who have never performed that action historically.
- Fiori Launchpad access logs showing navigation to the Manage Payment Blocks tile by users without a business justification.
Detection Strategies
- Review SAP Security Audit Log (SM20) entries for the Fiori app and correlate the acting user against the roles authorized for payment block maintenance.
- Enable Read Access Logging (RAL) on the OData service backing Manage Payment Blocks to capture which users retrieve or modify records.
- Compare change documents on financial documents against the list of users expected to maintain payment blocks and alert on deviations.
Monitoring Recommendations
- Ingest SAP Security Audit Log, RAL, and change document data into a central SIEM for correlation with identity and HR data.
- Build alerting on first-time access to the Manage Payment Blocks service by any user and on bulk release of payment blocks within a short time window.
- Track failed and successful authorization checks around the SAP Finance (FI) module to identify probing of restricted functions.
How to Mitigate CVE-2025-42915
Immediate Actions Required
- Apply the SAP-provided patch referenced in SAP Note #3409013 during the next available maintenance window.
- Review which users currently hold access to the Manage Payment Blocks Fiori tile and remove assignments that are not required.
- Audit recent payment block changes to confirm no unauthorized modifications occurred before patching.
Patch Information
SAP addressed CVE-2025-42915 as part of SAP Security Patch Day. Customers should consult SAP Note #3409013 for the exact support package and kernel patch levels that remediate the missing authorization check. Additional release details are summarized on the SAP Security Patch Day portal.
Workarounds
- Restrict access to the Manage Payment Blocks Fiori tile at the catalog or group level so only approved roles can launch it.
- Tighten PFCG role authorizations for the underlying FI transactions and OData services to enforce group-based restrictions until the patch is deployed.
- Monitor and alert on any invocation of the affected OData service by non-authorized users as a compensating control.
# Configuration example
# Identify users assigned to the Manage Payment Blocks Fiori catalog
# via transaction SUIM, then remove unneeded assignments in PFCG.
# Example audit query against the Security Audit Log in SM20:
# Event class: Transaction / RFC / Fiori
# Filter: User <> <authorized_AP_users>
# Object = Manage Payment Blocks service
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

