CVE-2023-35870
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 · uneditedWhen creating a journal entry template in SAP S/4HANA (Manage Journal Entry Template) - versions S4CORE 104, 105, 106, 107, an attacker could intercept the save request and change the template, leading to an impact on confidentiality and integrity of the resource. Furthermore, a standard template could be deleted, hence making the resource temporarily unavailable.
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 · high confidenceThis is an authorization bypass vulnerability in SAP S/4HANA's Manage Journal Entry Template functionality. An attacker can intercept the save request and modify or delete journal entry templates they should not have access to, affecting confidentiality and integrity. Additionally, standard templates can be deleted, causing availability impact.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 104= 105= 106= 107CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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.
-
Identify the installed S4CORE versionExecute transaction code SM51 in SAP GUI to view the system release and kernel version. Alternatively, use transaction code SLICENSE or check the SAP Note for the S4CORE version installed in your system.Affected if The S4CORE version is 104, 105, 106, or 107.
-
Determine if Manage Journal Entry Template is in useCheck for the Fiori application 'Manage Journal Entry Templates' (Fiori ID F0100) or the corresponding transaction code in your system. Query the Fiori app catalog or use transaction code /n/UI2/FLPD_CUST to review deployed apps.Affected if The Manage Journal Entry Template functionality is deployed or accessible in the system.
-
Review authorization roles for Journal Entry Template operationsUse transaction code PFCG to examine roles assigned to users who have access to journal entry template management. Check for authorization objects F_BKPF_BUK, F_BKPF_GSB, and F_JEST to verify proper segregation of duties.Affected if Users have roles granting template creation, modification, or deletion without proper restrictive authorization checks.
-
Audit recent template modifications in the systemExecute transaction code JBRF (Journal Entry Template) or review audit logs via transaction code RSusr003 or SLG1 for object JRA. Check for unauthorized template changes or deletions in the application logs.Affected if Template modifications or deletions exist that were performed by users lacking explicit authorization for those specific templates.
You are affected if your S4CORE version is 104, 105, 106, or 107 and the Manage Journal Entry Template functionality is accessible without proper authorization controls on save requests.
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 patches for the affected S4CORE versions (104, 105, 106, 107). Implement proper authorization checks on save requests to verify user permissions before allowing template creation, modification, or deletion.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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 $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35870 — 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-2023-35870 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