# CVE-2025-42876: Missing Authorization Check in SAP S/4 HANA Private Cloud (Financials General Ledger)

> An authenticated attacker can read sensitive data and modify documents across all company codes due to missing authorization checks in SAP S/4 HANA Financials.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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:** 9 Dec 2025
- **Updated:** 9 Dec 2025
- **Also known as:** GHSA-524p-rwpg-qg57

## What is CVE-2025-42876?

CVE-2025-42876 is a high-severity missing authorization vulnerability in SAP_SE SAP S/4 HANA Private Cloud (Financials General Ledger), published on 9 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Due to a Missing Authorization Check vulnerability in SAP S/4 HANA Private Cloud (Financials General Ledger), an authenticated attacker with authorization limited to a single company code could read sensitive data and post or modify documents across all company codes. Successful exploitation could result in a high impact to confidentiality and a low impact to integrity, while availability remains unaffected.

Weakness: CWE-405 (Asymmetric Resource Consumption (Amplification))

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


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

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

## Is CVE-2025-42876 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-42876 is a high-severity missing authorization vulnerability in SAP_SE SAP S/4 HANA Private Cloud (Financials General Ledger), published on 9 Dec 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-42876 in the wild and no public exploit code.

Affected product: SAP_SE SAP S/4 HANA Private Cloud (Financials General Ledger). 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-42876/ (Markdown: https://insights.sbomify.com/CVE-2025-42876/index.md)
```

## Sources

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

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