VulnerabilityPublished 14 Oct 2025

CVE-2025-42939: SAP S/4HANA (Manage Processing Rules – For Bank Statements) · Incorrect Authorization

Affects SAP S/4HANA (Manage Processing Rules – For Bank Statements)Source CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 13% 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:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
SAP_SE SAP S/4HANA (Manage Processing Rules - For Bank Statements)	Affected =105 =106 =107 =108 =109	Fixed in–

AI-suggested

1. Apply SAP vendor patches promptly once they become available for the affected versions (S4CORE 104-109). 2. Restrict user privileges to the minimum necessary, especially limiting access to Manage Processing Rules functionality to trusted personnel. 3. Implement strong authentication mechanisms, including multi-factor authentication, to reduce the risk of credential compromise. 4. Monitor logs and audit trails for unusual deletions or modifications of processing rules, setting alerts for anomalous activities. 5. Conduct regular reviews of shared processing rules and their conditions to detect unauthorized changes early. 6. Employ network segmentation and access controls to limit exposure of SAP systems to only authorized users and systems. 7. Educate users about phishing and credential security to prevent unauthorized access. 8. Consider deploying application-layer firewalls or SAP-specific security tools that can detect and block suspicious parameter tampering attempts.

Description

CVE-2025-42939 is a medium severity vulnerability in SAP S/4HANA's Manage Processing Rules for Bank Statements module. It allows an authenticated attacker with basic privileges to delete conditions from any shared processing rule by tampering with request parameters, due to missing authorization checks. This compromises the integrity of the application but does not affect confidentiality or availability. The vulnerability affects multiple versions from S4CORE 104 through 109. Exploitation requires authentication but no user interaction. No known exploits are currently reported in the wild. European organizations using SAP S/4HANA for financial processing are at risk of unauthorized modification of bank statement processing rules, potentially disrupting financial workflows and compliance. Mitigation involves applying vendor patches once available, restricting user privileges, and monitoring for anomalous rule changes. Countries with significant SAP S/4HANA adoption and strong financial sectors, such as Germany, France, and the UK, are most likely to be impacted.

Impact

For European organizations, this vulnerability poses a risk to the integrity of financial processing workflows within SAP S/4HANA environments. Unauthorized deletion of processing rule conditions can lead to incorrect handling of bank statements, potentially causing financial discrepancies, errors in automated reconciliation, and compliance issues with financial regulations such as GDPR and SOX. While confidentiality and availability remain unaffected, the integrity compromise could undermine trust in financial data and reporting. Organizations in sectors with heavy reliance on SAP S/4HANA for financial operations—such as banking, manufacturing, and large enterprises—may face operational disruptions and increased audit scrutiny. The requirement for authenticated access limits the threat to insiders or attackers who have compromised credentials, emphasizing the importance of strong identity and access management. Given the widespread use of SAP in Europe, the impact could be significant if exploited at scale or combined with other attack vectors.

Summary

CVE-2025-42939 is an authorization bypass vulnerability classified under CWE-863 affecting SAP SE's SAP S/4HANA product, specifically the Manage Processing Rules functionality for bank statements. The flaw arises because the application fails to properly verify authorization when processing requests to delete conditions from shared processing rules. An attacker who is authenticated with basic privileges can manipulate request parameters to delete conditions from any shared rule belonging to any user. This unauthorized deletion compromises the integrity of the processing rules, potentially altering how bank statements are handled within the system. The vulnerability does not impact confidentiality or availability, as it does not expose sensitive data or cause denial of service. It affects SAP S/4HANA versions S4CORE 104 through 109. Exploitation requires the attacker to have valid credentials but does not require additional user interaction, making it relatively straightforward once access is obtained. No public exploits have been reported to date, and no patches are currently linked, indicating that organizations should prioritize monitoring and access control until vendor fixes are released. The vulnerability score is 4.3 (medium severity) based on CVSS v3.1, reflecting the moderate impact and ease of exploitation given authenticated access.

CWE-863Incorrect Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #17OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Oct 2025, 11:58 UTC

WeaknessesCWE-863

Technical details

References

Community reviews

Related threats