Security readout for executives and security teams
Plain-English summary
This vulnerability affects SAP S/4HANA journal entry template management. A user with some access could tamper with a save request to change or delete templates, creating risk to financial process integrity and temporary disruption. It is not described as unauthenticated or actively exploited in the provided sources.
Executive priority
Treat as a moderate business risk for organizations using affected SAP S/4HANA finance workflows. Prioritize remediation in normal SAP security patch cycles, sooner where journal templates support critical reporting or posting controls.
Technical view
CVE-2023-35870 is an improper access control issue in SAP S/4HANA Manage Journal Entry Template, affecting S4CORE 104, 105, 106, and 107. CVSS 3.1 is 6.3: network reachable, low privileges required, no user interaction, with low confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to SAP S/4HANA systems running affected S4CORE versions where Manage Journal Entry Template is available to users whose requests could be altered.
Exploitation context
The source describes a low-privileged attacker intercepting a save request and altering or deleting a template. The CVE is not listed as KEV, and no provided source states active exploitation.
Researcher notes
Evidence supports improper access control with request tampering against template save operations. The public bundle does not include detailed SAP Note remediation text, proof-of-concept evidence, or exploitation telemetry, so avoid assumptions beyond affected versions and stated impact.
Mitigation direction
- Review SAP Note 3341211 for official correction guidance.
- Apply SAP-provided fixes or workarounds for affected S4CORE releases.
- Restrict journal entry template management to authorized finance or administration users.
- Monitor template create, update, and delete activity for unexpected changes.
Validation and detection
- Inventory SAP S/4HANA systems and identify S4CORE 104, 105, 106, or 107.
- Confirm whether Manage Journal Entry Template is enabled and used.
- Check SAP maintenance status against SAP Note 3341211.
- Review recent journal entry template changes and deletions for anomalies.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-732: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2023-35870 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L2.83.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://me.sap.com/notes/3341211CVE reference
- https://www.sap.com/documents/2022/02/fa865ea4-167e-0010-bca6-c68f7e60039b.htmlCVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incorrect Permission Assignment for Critical Resource
Incorrect Permission Assignment for Critical Resource represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.