# CVE-2026-76961: Cross-Site Request Forgery (CSRF) vulnerability in SAP S/4HANA (Finance for Advanced Payment Management)

> An attacker can trick authenticated users into performing unintended actions in SAP S/4HANA Finance via CSRF, affecting confidentiality and integrity.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Sep 2026
- **Updated:** 9 Sep 2026
- **Also known as:** GHSA-4hm3-8c23-x5v9

## What is CVE-2026-76961?

CVE-2026-76961 is a low-severity vulnerability in SAP_SE SAP S/4HANA (Finance for Advanced Payment Management), published on 8 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

SAP S/4HANA Finance (Advanced Payment Management) does not perform sufficient Cross-Site Request Forgery protection on certain requests, due to this an attacker with low privileges could craft a malicious link or page. If an authenticated victim interacts with it, unintended actions could be triggered on the web server on their behalf. This results in a low impact on confidentiality and integrity. There is no impact on availability.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2026-76961?


## How do I fix CVE-2026-76961?

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

## Is CVE-2026-76961 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-76961 and fix it if it is affected.

What it is: CVE-2026-76961 is a low-severity vulnerability in SAP_SE SAP S/4HANA (Finance for Advanced Payment Management), published on 8 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-76961 in the wild and no public exploit code.

Affected product: SAP_SE SAP S/4HANA (Finance for Advanced Payment Management). 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-2026-76961/ (Markdown: https://insights.sbomify.com/CVE-2026-76961/index.md)
```

## Sources

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

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