CVE-2025-42950: SAP Landscape Transformation (Analysis Platform) · Improper Control of Generation of Code
Affects SAP Landscape Transformation (Analysis Platform)Source CVE Database V5
Not known to be exploited · CVSS 9.9 Critical.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 52% 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:HExploitation evidence
Disclosed: evidence found.
CVE published 12 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SAP_SE SAP Landscape Transformation (Analysis Platform) | Affected
| Fixed in– |
AI-suggested
1. Immediate mitigation should focus on restricting access to the vulnerable RFC function modules by implementing strict authorization checks and network-level segmentation to limit exposure. 2. Monitor SAP system logs and RFC call activity for unusual or unauthorized code execution attempts. 3. Apply SAP security notes and patches as soon as they are released by SAP for the affected SLT versions. 4. Enforce the principle of least privilege by reviewing and minimizing user privileges, especially for accounts with RFC access. 5. Implement multi-factor authentication (MFA) for SAP user accounts to reduce the risk of credential compromise. 6. Conduct regular security audits and vulnerability assessments focused on SAP environments to detect misconfigurations or unauthorized changes. 7. Employ runtime application self-protection (RASP) or SAP-specific security tools that can detect and block abnormal ABAP code execution. 8. Establish incident response plans tailored to SAP system compromises to enable rapid containment and recovery. 9. Educate SAP administrators and users about the risks of this vulnerability and best practices for secure SAP operations. These steps go beyond generic advice by focusing on SAP-specific controls, proactive monitoring, and rapid patch management.
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.