dbcve.org
Customer Relationship Management Webclient UiApplication · Sap

CVE-2023-29188

MEDIUM · 5.4 CVSS v3.1 Published 2023-05-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
SAP CRM WebClient UI - versions SAPSCORE 129, S4FND 102, S4FND 103, S4FND 104, S4FND 105, S4FND 106, S4FND 107, WEBCUIF 701, WEBCUIF 731, WEBCUIF 746, WEBCUIF 747, WEBCUIF 748, WEBCUIF 800, WEBCUIF 801, does not sufficiently encode user-controlled inputs, resulting in Cross-Site Scripting (XSS) vulnerability. After successful exploitation, an attacker with user level access can read and modify some sensitive information but cannot delete the data.

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 confidence

Cross-Site Scripting (XSS) vulnerability in SAP CRM WebClient UI due to insufficient encoding of user-controlled inputs. Affected components include SAPSCORE, S4FND (versions 102-107), and WEBCUIF (versions 701, 731, 746-748, 800-801). An authenticated user with standard access can inject malicious scripts that execute in the context of other users' sessions.

MitigationApply SAP security patches for the affected versions. Implement proper output encoding for all user-controlled inputs in the WebClient UI framework.

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
Customer Relationship Management Webclient UiApplication
Affected:= 7.01= 7.31= 7.46= 7.47= 7.48= 8.00= 8.01
S4fndApplication
Affected:= 1.02= 102= 103= 104= 105= 106= 107
SapscoreApplication
Affected:= 129

CVSS 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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed SAP product component
    Check which SAP component is installed: execute transaction code SPAM or use transaction SE16N to view table CVERS_COMPONENTS to list installed SAP components. Look for SAPSCORE, S4FND, or WEBCUIF.
    Affected if The component SAPSCORE, S4FND, or WEBCUIF is installed on the system
  2. Check SAPSCORE version
    Execute transaction code SM37 or use ABAP report to query system version. Navigate to SAP System -> Status to view SAP Release and SAP Kernel version. Look specifically for SAPSCORE component version.
    Affected if SAPSCORE version is exactly 129
  3. Check S4FND version
    Execute transaction code SPAM and check component version for S4FND. Alternatively use SAINT to view installed software components. Look for S4FND version in the range 102-107 or version 1.02.
    Affected if S4FND version equals 1.02 or is between 102 and 107 inclusive
  4. Check WEBCUIF version
    Execute transaction code SE16 and query table COMPONENT_INFO or use SPAM to view installed components. Look for WEBCUIF version 701, 731, 746, 747, 748, 800, or 801.
    Affected if WEBCUIF version is 701, 731, 746, 747, 748, 800, or 801
  5. Verify WebClient UI is enabled
    Check if WebClient UI framework is active by reviewing transaction SICF (SAP Internet Communication Manager) for WebClient UI services, or check if transaction CRM_UI or similar WebClient UI transactions are accessible to users.
    Affected if WebClient UI is active and accessible to authenticated users

The system is affected if SAPSCORE version 129, S4FND versions 102-107 or 1.02, or WEBCUIF versions 701/731/746-748/800-801 is installed AND WebClient UI framework is enabled and accessible to authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply SAP security patches for the affected versions. Implement proper output encoding for all user-controlled inputs in the WebClient UI framework.

Recommended fix Moderate confidence

WEBCUIF 748+ or S4FND 105+ or SAPSCORE 130+ (depending on your component)

  1. 1. Identify the current version of the SAP component (WEBCUIF or S4FND or SAPSCORE) in your system using SAP transaction SM37 or system profile.
  2. 2. For WEBCUIF (WebClient UI) components: Upgrade to WEBCUIF 748 or higher (800 or 801).
  3. 3. For S4FND (S/4HANA Foundation) components: Upgrade to S4FND 105 or higher (106 or 107).
  4. 4. For SAPSCORE components: Upgrade to a version higher than 129 (check SAP notes for the latest patched version).
  5. 5. After upgrade, verify the system landscape to ensure all dependent components are compatible.
  6. 6. Test critical business workflows in a non-production environment before deploying the upgrade to production.
  7. 7. Apply SAP Security Notes (refer to SAP support portal for CVE-2023-29188 specific notes) after the upgrade to ensure complete remediation.
Caveat Custom enhancements or UI5 modifications may require testing/rework after upgrade; ensure compatibility with the target WEBCUIF/S4FND version in SAP S/4HANA compatibility matrix

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Customer Relationship Management Webclient Ui Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-29188 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-29188 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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