# CVE-2019-0276: Missing authorization in Banking services from SAP 9.0 (FSAPPL)

> An authenticated user can escalate privileges due to inadequate authorization checks in SAP Banking Services and S/4HANA Financial Products Subledger.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 12 Mar 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-7245-97xv-qh8g

## What is CVE-2019-0276?

CVE-2019-0276 is a high-severity missing authorization vulnerability in Banking services from SAP 9.0 (FSAPPL), published on 12 Mar 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Banking services from SAP 9.0 (FSAPPL version 5) and SAP S/4HANA Financial Products Subledger (S4FPSL, version 1) performs an inadequate authorization check for an authenticated user, potentially resulting in escalation of privileges.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2019-0276?

It affects 2 products.


Products: Sap Banking Services From Sap, Sap S\/4hana Financial Products Subledger.

## How do I fix CVE-2019-0276?

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

## Is CVE-2019-0276 being exploited?

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

## Other vulnerabilities in Banking services from SAP 9.0 (FSAPPL)

- [CVE-2020-6233](https://insights.sbomify.com/CVE-2020-6233/): Missing authorization in SAP S/4 HANA (Financial Products Subledger and Banking Services) (FSAPPL) (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-0276 and fix it if it is affected.

What it is: CVE-2019-0276 is a high-severity missing authorization vulnerability in Banking services from SAP 9.0 (FSAPPL), published on 12 Mar 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-0276 in the wild and no public exploit code.

Affected product: Banking services from SAP 9.0 (FSAPPL). 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-2019-0276/ (Markdown: https://insights.sbomify.com/CVE-2019-0276/index.md)
```

## Sources

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

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