SAP S/4HANA: Code injection in Manage Substitution/Validation Rules
Summary
The Manage Substitution/Validation Rules functionality of SAP S/4HANA does not sufficiently validate input processed by its rule definition feature, which uses a domain-specific scripting language. An authenticated attacker with specific business privileges can submit crafted input that is interpreted as ABAP code.
Successful exploitation could lead to full compromise of the affected system with high impact on confidentiality, integrity and availability.
Affected
- SAP S/4HANA (Manage Substitution/Validation Rules), S4CORE 105, 106, 107, 108 and 109
- Default configuration: unaffected according to the CVE record
Fixed in
Unknown. Correction is provided in SAP Security Note 3805589; check the note for the corrected support packages.
Workaround
Unknown. Sources disagree on whether a workaround exists. Check SAP Security Note 3805589. Until patched, restrict users who hold rule-definition roles.
Exploitation
- CISA SSVC assessment: Exploitation none, Automatable no.
- No public exploit code confirmed at the time of analysis.
Our recommendation
- Apply the correction from SAP Security Note 3805589 with priority, after verifying the affected support packages.
- Check whether the Manage Substitution/Validation Rules apps are in use.
- Review and limit users with rule-definition roles according to least privilege.
- Review audit logs and changes to substitution and validation rules for past misuse.
Public exploits
PoC-in-GitHub, Metasploit and Exploit-DB list nothing for this CVE.
Research sources
- SAP Security Note 3805589 me.sap.com
- SAP Security Patch Day url.sap
- SAP Security Notes October 2026 (SAP Knowledge Base) support.sap.com
Researched and written up in English and German by an AI (Claude by Anthropic) based on NVD, CISA, EPSS and the sources listed. The vendor information is authoritative. Researched on 30 Oct 2026, 15:27.
Original description (NVD)
SAP S/4HANA (Manage Substitution/Validation Rules) does not sufficiently validate input processed by rule definition functionality that utilizes a domain-specific scripting language. An authenticated attacker with specific business privileges could submit specially crafted input, which is interpreted as executable ABAP code by the rule processing logic. Successful exploitation could allow the attacker to execute ABAP arbitrary code into the system, resulting in full compromise of the affected system and high impact on confidentiality, integrity, and availability of the system.
NVD references (2)
Sources
The tracker combines official, freely usable data sources – updated continuously:
- NVD (NIST) – CVEs, rating (CVSS), affected products
- CISA KEV – vulnerabilities confirmed by CISA as actively exploited
- CISA Vulnrichment – CISA assessment (SSVC) in the official CVE record
- FIRST EPSS – probability of exploitation
- Microsoft MSRC – Patch Tuesday: vulnerabilities, severity, updates
- PoC-in-GitHub – public proof-of-concept repositories
- Metasploit (Rapid7) – modules of the Metasploit Framework
- Exploit-DB (OffSec) – archive of public exploits (links only)
- Patch days: official vendor pages (linked per vendor) (Vendor patch days)
This product uses data from the NVD API but is not endorsed or certified by the NVD. EPSS data © FIRST.org.
Affected? We can help.
We check whether your systems are affected, install updates and close the gap – continuously with the System Health Checker if you wish.