CVE-2025-31330
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 · uneditedSAP Landscape Transformation (SLT) 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 confidenceSAP Landscape Transformation (SLT) contains a vulnerability in a function module exposed via RFC that allows an authenticated attacker with standard user privileges to inject arbitrary ABAP code, bypassing authorization checks. This effectively creates a backdoor enabling full system compromise across confidentiality, integrity, and availability.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm SAP SLT installationExecute transaction code SLM0 or check system table T000 for SLT-related client configurations. Query table SAPSLND for installed SLT components.Affected if SLT is installed and active in the SAP system
-
Identify RFC-enabled function modules in SLTUse transaction SE37 or SM59 to list function modules with RFC capability within the SLT namespace (e.g., /SLND/*). Check table TFDIR for function modules in SLT-related function groups.Affected if RFC-enabled function modules exist in the SLT deployment
-
Review RFC authorization assignments for standard usersExecute transaction SUIM or use table USOBX to examine authorization objects assigned to standard (non-privileged) users for SLT RFC function modules. Check if S_RFC or S_DEVELOP authorizations permit execution.Affected if Standard users have RFC execution permissions on SLT function modules
-
Audit custom or unexpected function modulesReview transaction SE80 for any custom ABAP code within SLT-related packages. Compare function module names against known SAP standard SLT modules to identify anomalies.Affected if Unexpected or custom function modules are present in SLT that deviate from standard installation
A user is affected if SAP SLT is deployed with RFC-exposed function modules that grant standard users the ability to execute arbitrary ABAP code, enabling system compromise.
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 SAP security notes/patches for CVE-2025-31330 immediately; review and restrict RFC-exposed function module authorizations in SLT to minimize attack surface.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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 $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31330 — 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-31330 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