dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-43010

HIGH · 8.3 CVSS v3.1 Published 2025-05-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
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 Cloud Private Edition or on Premise (SCM Master Data Layer (MDL)) allows an authenticated attacker with SAP standard authorization to execute a certain function module remotely and replace arbitrary ABAP programs, including SAP standard programs. This is due to lack of input validation and no authorization checks. This has low Confidentiality impact but high impact on integrity and availability to the application.

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

SAP S/4HANA Cloud Private Edition or on Premise contains a vulnerability in the SCM Master Data Layer (MDL) component where an authenticated attacker with standard SAP authorization can execute a specific function module remotely to replace arbitrary ABAP programs, including SAP standard programs, due to missing input validation and authorization checks.

MitigationApply the relevant SAP security patch for this vulnerability and review/restrict authorizations for the affected function module to prevent unauthorized ABAP program replacement.

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
Unchanged
Confidentiality
Low
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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. Identify SAP S/4HANA installation
    Execute transaction SM51 to view the SAP system name and release, or use transaction SWO1 to query the system version via 'SAP System Information'. Alternatively, check transaction SIDET to confirm the system type is S/4HANA Cloud Private Edition or On-Premise.
    Affected if The system is not SAP S/4HANA Cloud Private Edition or On-Premise (different SAP products are not affected).
  2. Verify SCM Master Data Layer component is installed
    Execute transaction SA03 or use transaction SE16 to view table CVERS (Component Versions). Look for component name starting with 'SCM' or 'MDL' in the installed components list. Alternatively, check transaction SE11 for table MDM_COMPONENTS if it exists in your system.
    Affected if The SCM Master Data Layer (MDL) component does not appear in the installed components, indicating the affected component is not present.
  3. Locate the vulnerable function module
    Use transaction SE37 (Function Builder) and search for function modules related to ABAP program replacement within the MDL namespace. Check transaction SE84 for object dependencies, or query table TFDIR for function modules in the MDL-related packages that handle program replacements.
    Affected if A function module capable of replacing ABAP programs (including SAP standard programs) exists in the MDL component without proper authorization checks.
  4. Review authorization assignments for the function module
    Execute transaction SU53 immediately after testing access to the suspected function module to review authorization failures. Use transaction SUIM to search for roles containing the function module in authorization objects S_PROGRAM or S_DEVELOP. Check transaction auth_debug for recent authorization violations.
    Affected if Standard users with basic SAP authorizations can execute the program replacement function module, indicating the vulnerability is exploitable in the current configuration.

The system is affected if it is S/4HANA Cloud Private Edition or On-Premise with the SCM Master Data Layer component installed and standard users have authorization to execute the program replacement function module.

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

Apply the relevant SAP security patch for this vulnerability and review/restrict authorizations for the affected function module to prevent unauthorized ABAP program replacement.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-43010 — 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-43010 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