# CVE-2025-27433: Broken Access Control vulnerabilities in SAP S/4HANA (Manage Bank Statements)

> An authenticated attacker can bypass restrictions to upload files to reversed bank statements in SAP S/4HANA, 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:** 11 Mar 2025
- **Updated:** 11 Mar 2025
- **Also known as:** GHSA-h4p3-cg85-78c7

## What is CVE-2025-27433?

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

### Official description

The Manage Bank Statements in SAP S/4HANA allows authenticated attacker to bypass certain functionality restrictions of the application and upload files to a reversed bank statement. This vulnerability has a low impact on the application's integrity, with no effect on confidentiality and availability of the application.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2025-27433 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-27433 is a medium-severity missing authorization vulnerability in SAP_SE SAP S/4HANA (Manage Bank Statements), published on 11 Mar 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-27433 in the wild and no public exploit code.

Affected product: SAP_SE SAP S/4HANA (Manage 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-27433/ (Markdown: https://insights.sbomify.com/CVE-2025-27433/index.md)
```

## Sources

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

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