# CVE-2025-42993: Missing Authorization Check in SAP S/4HANA (Enterprise Event Enablement)

> An attacker with Inbound Binding Configuration access can create an RFC destination to execute code with high-privilege user rights.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jun 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-hhjp-qj76-2j9m

## What is CVE-2025-42993?

CVE-2025-42993 is a medium-severity missing authorization vulnerability in SAP_SE SAP S/4HANA (Enterprise Event Enablement), published on 10 Jun 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Due to a missing authorization check vulnerability in SAP S/4HANA (Enterprise Event Enablement), an attacker with access to the Inbound Binding Configuration could create an RFC destination and assign an arbitrary high-privilege user. This allows the attacker to consume events via the RFC destination, leading to code execution under the privileges of the assigned high-privilege user. While the vulnerability has a low impact on Availability, it significantly poses a high risk to both Confidentiality and Integrity.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2025-42993 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-42993 is a medium-severity missing authorization vulnerability in SAP_SE SAP S/4HANA (Enterprise Event Enablement), published on 10 Jun 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-42993 in the wild and no public exploit code.

Affected product: SAP_SE SAP S/4HANA (Enterprise Event Enablement). 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-42993/ (Markdown: https://insights.sbomify.com/CVE-2025-42993/index.md)
```

## Sources

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

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