dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-42957

CRITICAL · 9.9 CVSS v3.1 Published 2025-08-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
SAP S/4HANA allows an attacker with user privileges to exploit a vulnerability in the function module exposed via RFC. This flaw enables the injection of arbitrary ABAP code into the system, bypassing essential authorization checks. This vulnerability effectively functions as a backdoor, creating the risk of full system compromise, undermining the confidentiality, integrity and availability of the system.

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 confidence

This is a critical vulnerability in SAP S/4HANA where an attacker with basic user privileges can exploit a function module exposed via RFC (Remote Function Call). The flaw allows injection of arbitrary ABAP code into the system while bypassing essential authorization checks, effectively creating a backdoor that enables full system compromise.

MitigationImmediately identify and disable or secure the vulnerable RFC-exposed function module, apply available SAP security patches, and conduct a comprehensive review of RFC authorization assignments to prevent exploitation.

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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify SAP S/4HANA version
    Execute transaction SM37 or use SAP MII version check to determine the installed SAP S/4HANA version. Compare against known affected version ranges for this CVE.
    Affected if The installed version falls within the affected version range for CVE-2025-42957 and RFC functionality is active.
  2. Confirm RFC is enabled
    Execute transaction SM59 and check if RFC destinations are configured and active. Also check transaction SRTM for RFC monitoring capabilities.
    Affected if RFC is enabled and exposed function modules are accessible from external or internal RFC destinations.
  3. Identify RFC-exposed function modules
    Use transaction SE37 with function module search, or execute report RSFUNCTIONBUILDER_HELP to list function modules with 'Remote-Enabled Module' (RFC) attribute marked as enabled. Focus on modules in function groups that allow data manipulation or code execution.
    Affected if A function module with RFC exposure exists that accepts user input and can be leveraged for ABAP code injection without proper authorization validation.
  4. Review RFC authorization assignments
    Execute transaction SUIM to filter for roles containing authorization object S_RFC with ACTVT values that grant RFC access. Check transaction SU53 after attempted RFC calls to identify missing authorization checks.
    Affected if Users with basic privileges have RFC authorization to function modules that perform privileged operations without proper ABAP code authorization checks.
  5. Audit function module ABAP logic for injection points
    Use transaction SE37 to examine source code of RFC-enabled function modules, looking for dynamic ABAP execution statements (SUBMIT, CALL TRANSACTION, REPLACE PATTERN) or direct database modification without input validation.
    Affected if An RFC-enabled function module contains logic that can be manipulated to execute arbitrary ABAP commands or bypass security checks.

A user is affected if running a vulnerable SAP S/4HANA version with RFC-enabled function modules that allow arbitrary ABAP code injection due to missing authorization checks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately identify and disable or secure the vulnerable RFC-exposed function module, apply available SAP security patches, and conduct a comprehensive review of RFC authorization assignments to prevent exploitation.

Have this fixed Scoped from the published advisory
  • Consultation12.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
60.0 hours of engineering $10,560
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $16,896.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-42957 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-42957 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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