{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-42993 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-42993 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2025-42993 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2025-42993 in the wild and no public exploit code.\n\nAffected 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.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-42993/ (Markdown: https://insights.sbomify.com/CVE-2025-42993/index.md)","id":"CVE-2025-42993","markdown":"https://insights.sbomify.com/CVE-2025-42993/index.md","name":"CVE-2025-42993","record":{"aliases":["GHSA-hhjp-qj76-2j9m"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"SAP S/4HANA","requires_auth":"high_privilege","summary":"An attacker with Inbound Binding Configuration access can create an RFC destination to execute code with high-privilege user rights.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"sap","cpe":[],"cvss":{"score":6.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Missing Authorization Check in SAP S/4HANA (Enterprise Event Enablement)","id":"CVE-2025-42993","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Multiple vulnerabilities in SAP MDM Server","id":"CVE-2025-42994"},"packages":[],"prev":{"headline":"Multiple Privilege Escalation Vulnerabilities in SAPCAR","id":"CVE-2025-42992"},"products":["SAP S/4HANA (Enterprise Event Enablement)"],"published":"2025-06-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-02-26","vendors":["SAP_SE"]},"summary":"An attacker with Inbound Binding Configuration access can create an RFC destination to execute code with high-privilege user rights.","url":"https://insights.sbomify.com/CVE-2025-42993/"}