dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-42880

CRITICAL · 9.9 CVSS v3.1 Published 2025-12-09
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
Due to missing input sanitation, SAP Solution Manager allows an authenticated attacker to insert malicious code when calling a remote-enabled function module. This could provide the attacker with full control of the system hence leading to high impact on 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 · high confidence

This is a code injection vulnerability in SAP Solution Manager caused by missing input validation. An authenticated attacker can inject malicious code through remote-enabled function modules, potentially achieving full system control with impact on confidentiality, integrity, and availability.

MitigationImplement strict input validation and sanitization on all remote-enabled function module parameters; apply vendor patches when available and restrict access to sensitive function modules to authorized personnel only.

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. Identify SAP Solution Manager installation
    Check if SAP Solution Manager (SAP SolMan) is installed on the system. Look for SAP-related processes, directories (typically under /usr/sap or /sapmnt), or check SAP kernel version via SAP transaction SM51 or command 'sapcontrol -nr <instance> -function GetVersionInfo'.
    Affected if SAP Solution Manager is present on the system.
  2. Determine SAP Solution Manager version
    Access SAP transaction SM51 to view the release version, or use command 'sapcontrol -nr <instance> -function GetVersionInfo' to retrieve the specific version number. Compare against any known affected version ranges provided by SAP security notes.
    Affected if The installed version falls within any vulnerable version range identified by SAP.
  3. Check for remote-enabled function modules
    Use SAP transaction SE37 (Function Builder) or table FDIR to list function modules with the attribute 'Remote-Enabled' (RFC checkbox marked). Focus on custom function modules in namespaces like /SAPSLS/ or /BTI/ that may accept user input.
    Affected if Remote-enabled function modules exist, especially custom or legacy modules that accept external parameters.
  4. Review authentication and access controls
    Use transaction SU01 to review user accounts with access to remote-enabled function modules, and transaction SM37 to monitor background jobs that invoke RFC-enabled modules. Check if critical RFC destinations (transaction SM59) allow external access.
    Affected if External or untrusted users have RFC access, or RFC destinations are exposed to untrusted networks.
  5. Inspect recent RFC/remote function call logs
    Review transaction SLG1 (Application Log) for entries related to RFC calls, and check transaction SM37 for recent job executions involving function modules. Look for unusual or injection-pattern payloads in parameter values.
    Affected if Logs show unexpected parameter values or patterns consistent with injection attempts in RFC calls.

A user is affected if SAP Solution Manager is installed, the version is within a vulnerable range, and remote-enabled function modules are exposed to authenticated users without strict input validation on their parameters.

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

Implement strict input validation and sanitization on all remote-enabled function module parameters; apply vendor patches when available and restrict access to sensitive function modules to authorized personnel only.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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