Skip to main content
VulnerabilityPublished Updated

CVE-2025-31330: SAP Landscape Transformation (Analysis Platform) · Code Injection

Affects SAP Landscape Transformation (Analysis Platform)Source CVE Database V5

0

Not known to be exploited · CVSS 9.9 Critical.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
9.9Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Apr 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

  1. Immediately restrict access to the vulnerable RFC function modules to only trusted and necessary users, employing the principle of least privilege.
  2. Implement enhanced monitoring and logging of RFC calls and ABAP code execution to detect anomalous or unauthorized activities.
  3. Apply network segmentation and firewall rules to limit exposure of SAP SLT systems to untrusted networks.
  4. Regularly audit user privileges and remove or disable accounts that do not require SLT access.
  5. Once SAP releases official patches or updates addressing CVE-2025-31330, prioritize their deployment in all affected environments.
  6. Employ SAP’s Security Notes and tools such as SAP Solution Manager to monitor system health and compliance.
  7. Conduct thorough security assessments and penetration testing focused on RFC interfaces and code injection vectors.
  8. Educate SAP administrators and developers on secure coding practices and the risks of code injection vulnerabilities.
  9. Consider deploying runtime application self-protection (RASP) or similar technologies to detect and block injection attempts in real time.
  10. Maintain an incident response plan tailored to SAP system compromises to enable rapid containment and recovery.

Description

SAP 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.

References

Community reviews

Loading reviews…