CVE-2025-42993
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDue 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceMissing authorization check in SAP S/4HANA Enterprise Event Enablement allows attackers with Inbound Binding Configuration access to create RFC destinations and assign arbitrary high-privilege users. This enables event consumption via the RFC destination, resulting in code execution under the privileges of the assigned high-privilege user account.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify SAP S/4HANA versionExecute SAP transaction SM51 or use SAPMMC to view the installed SAP S/4HANA version and release. Compare against any known affected version ranges for Enterprise Event Enablement.Affected if SAP S/4HANA is running and Enterprise Event Enablement module is present
-
Verify Enterprise Event Enablement is enabledCheck SAP transaction SE11 or SPRO configuration for Enterprise Event Enablement module (Business Event Enablement / SAP Event Enablement). Look for related services in transaction SICF.Affected if Enterprise Event Enablement is active in the SAP system
-
Audit Inbound Binding Configuration accessUse SAP transaction SUIM or RSUSR002 to review users assigned to roles containing authorization object S_EVENT_BINDING (or similar inbound binding authorization objects). Check for excessive or unnecessary access.Affected if Users without proper admin privileges have Inbound Binding Configuration access
-
Inspect RFC destinations for unauthorized creationExecute SAP transaction SM59 to list RFC destinations. Look for newly created destinations pointing to unexpected targets, particularly those created recently or by non-administrator users.Affected if RFC destinations exist that were created by users without proper authorization or point to suspicious endpoints
-
Check for high-privilege user assignments in event bindingsReview Inbound Binding Configuration settings in transaction SPRO or related event management transactions. Verify that no arbitrary users (especially high-privilege accounts) have been assigned to event bindings.Affected if Arbitrary or high-privilege user accounts are assigned to event bindings without proper authorization
A user is affected if they run SAP S/4HANA with Enterprise Event Enablement enabled and have Inbound Binding Configuration accessible to non-administrative or unauthorized users who can create RFC destinations and assign high-privilege accounts.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the relevant SAP Security Note patch and implement proper authorization checks for Inbound Binding Configuration. Restrict access to trusted administrators only.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-42993 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-42993 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data