# CVE-2025-42960: Missing Authorization Check in SAP Business Warehouse and SAP BW/4HANA BEx Tools

> Authenticated attackers can bypass authorization checks to delete user table entries, impacting data integrity in SAP Business Warehouse.

- **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:** 8 Jul 2025
- **Updated:** 8 Jul 2025
- **Also known as:** GHSA-f4m2-6g8h-79gq

## What is CVE-2025-42960?

CVE-2025-42960 is a medium-severity missing authorization vulnerability in SAP_SE SAP Business Warehouse and SAP BW/4HANA BEx Tools, published on 8 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SAP Business Warehouse and SAP BW/4HANA BEx Tools allow an authenticated attacker to gain higher access levels than intended by exploiting improper authorization checks. This could potentially impact data integrity by allowing deletion of user table entries.�It has no impact on the confidentiality and availability of the application.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2025-42960 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-42960 is a medium-severity missing authorization vulnerability in SAP_SE SAP Business Warehouse and SAP BW/4HANA BEx Tools, published on 8 Jul 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-42960 in the wild and no public exploit code.

Affected product: SAP_SE SAP Business Warehouse and SAP BW/4HANA BEx Tools. 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-42960/ (Markdown: https://insights.sbomify.com/CVE-2025-42960/index.md)
```

## Sources

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

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