# CVE-2025-42939: Missing Authorization Check in SAP S/4HANA (Manage Processing Rules - For Bank Statements)

> An authenticated attacker can delete shared bank statement processing rules for any user due to missing authorization checks, compromising data integrity.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2025
- **Updated:** 14 Oct 2025
- **Also known as:** GHSA-h2f2-x9qf-59r2

## What is CVE-2025-42939?

CVE-2025-42939 is a medium-severity missing authorization vulnerability in SAP_SE SAP S/4HANA (Manage Processing Rules - For Bank Statements), published on 14 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SAP S/4HANA (Manage Processing Rules - For Bank Statements) allows an authenticated attacker with basic privileges to delete conditions from any shared rule of any user by tampering the request parameter. Due to missing authorization check, the attacker can delete shared rule conditions that should be restricted, compromising the integrity of the application without affecting its confidentiality or availability.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2025-42939?


## How do I fix CVE-2025-42939?

No fix has been published for CVE-2025-42939 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-42939 being exploited?

There is no known exploitation of CVE-2025-42939 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-42939 and fix it if it is affected.

What it is: CVE-2025-42939 is a medium-severity missing authorization vulnerability in SAP_SE SAP S/4HANA (Manage Processing Rules - For Bank Statements), published on 14 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-42939 in the wild and no public exploit code.

Affected product: SAP_SE SAP S/4HANA (Manage Processing Rules - For Bank Statements). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-42939/ (Markdown: https://insights.sbomify.com/CVE-2025-42939/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-42939
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-42939
- OSV: https://osv.dev/vulnerability/CVE-2025-42939

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-42939/
Summaries are generated and may contain mistakes; the official description above is the record.