CVE-2023-27897
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 · uneditedIn SAP CRM - versions 700, 701, 702, 712, 713, an attacker who is authenticated with a non-administrative role and a common remote execution authorization can use a vulnerable interface to execute an application function to perform actions which they would not normally be permitted to perform. Depending on the function executed, the attack can can have limited impact on confidentiality and integrity of non-critical user or application data and application availability.
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 · moderate confidenceIn SAP CRM versions 700-713, an authenticated attacker with a non-administrative role can exploit a vulnerable interface to execute application functions beyond their authorized permissions. This represents a privilege escalation/authorization bypass affecting confidentiality, integrity, and availability of non-critical application data.
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= 700= 701= 702= 712= 713CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/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 installed SAP CRM versionUse transaction code SM37 or check system information via SAP transaction 'System' > 'Status' to retrieve the CRM system version. Alternatively, query table CRMD_CUSTOMIZING or use SAPoCtrl command: SAPcontrol -nr <instance> -function GetVersionInfoAffected if The installed version is 700, 701, 702, 712, or 713
-
Verify user role assignmentsUse transaction code SUIM or PFCG to review all users assigned to the affected CRM roles. Check which users have non-administrative roles that include access to the vulnerable interfaceAffected if Non-administrative users exist with roles that could potentially access the vulnerable interface for function module execution
-
Audit function module execution logsUse transaction code SLG1 or ST03N to review application logs for function module executions. Filter by the vulnerable interface module and check for instances where non-administrative users executed functions outside their typical authorization scopeAffected if Logs show non-admin users executing functions via the vulnerable interface that fall outside their assigned role permissions
-
Review authorization tracesEnable and review authorization traces using transaction code STAUTHTRACE or run an authorization check via SU53 after suspect operations. Compare granted authorizations against the functions actually invokedAffected if Traces indicate authorization bypass events where users executed functions their roles should not permit
-
Inspect vulnerable interface accessibilityUse transaction code SE37 or SE80 to examine the specific function module/interface referenced in the security note. Verify if it can be called by users with non-administrative roles without proper authorization checksAffected if The interface permits execution by non-administrative users without enforcing proper authorization boundaries
A user is affected if they run SAP CRM versions 700-713 and have non-administrative users who can access the vulnerable interface to execute functions beyond their authorized permissions.
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 relevant SAP security notes/patches for CVE-2023-27897 and review/restrict affected authorization roles to enforce proper function module execution boundaries.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-27897 — 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-27897 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