# CVE-2019-0386: Missing authorization in S4HANA Sales (S4CORE)

> Authenticated users can escalate privileges in SAP ERP and S4HANA Sales due to missing authorization checks during order processing.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **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:** 13 Nov 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-wcf6-rgr3-qr83

## What is CVE-2019-0386?

CVE-2019-0386 is a medium-severity missing authorization vulnerability in SAP SE S4HANA Sales (S4CORE), published on 13 Nov 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Order processing in SAP ERP Sales (corrected in SAP_APPL 6.0, 6.02, 6.03, 6.04, 6.05, 6.06, 6.16, 6.17, 6.18) and S4HANA Sales (corrected in S4CORE 1.0, 1.01, 1.02, 1.03, 1.04) does not execute the required authorization checks for an authenticated user, which can result in an escalation of privileges.

Weakness: CWE-862 (Missing Authorization)

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

It affects 2 products.


Products: Sap Erp Sales, Sap S4hana Sales.

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

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

## Is CVE-2019-0386 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-0386 is a medium-severity missing authorization vulnerability in SAP SE S4HANA Sales (S4CORE), published on 13 Nov 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-0386 in the wild and no public exploit code.

Affected product: SAP SE S4HANA Sales (S4CORE). 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-0386/ (Markdown: https://insights.sbomify.com/CVE-2019-0386/index.md)
```

## Sources

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

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