Customer Relationship Management Webclient UiApplication · Sap

CVE-2023-24525

MEDIUM · 5.4 CVSS v3.1 Published 2023-02-14
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 WEBCUIF 748, 800, 801, S4FND 102, 103, does not sufficiently encode user-controlled inputs, resulting in Cross-Site Scripting (XSS) vulnerability. On successful exploitation an authenticated attacker can cause limited impact on confidentiality of the application.

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 confidence

SAP CRM WebClient UI versions WEBCUIF 748, 800, 801 and S4FND 102, 103 fail to properly encode user-controlled inputs in the web interface, allowing authenticated attackers to inject malicious scripts (XSS). The vulnerability exists in the UI framework's handling of input data that gets rendered in web pages.

MitigationApply SAP security patches for the affected WEBCUIF and S4FND versions. Implement proper input validation and output encoding for all user-controlled data rendered in the CRM WebClient UI pages.

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.00= 7.01= 7.02= 7.31= 7.40= 7.48= 7.50= 7.52= 8.00= 8.01
S4fndApplication
Affected:= 1.02= 1.03

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 SAP WEBCUIF version
    Execute transaction code SPAM or use SAP META version checker to view installed WEBCUIF component version. Check System > Status > SAP System Information for the WebClient UI framework version.
    Affected if The installed WEBCUIF version matches 7.00, 7.01, 7.02, 7.31, 7.40, 7.48, 7.50, 7.52, 8.00, or 8.01
  2. Identify SAP S4FND version
    Execute transaction code SPAM or check SAP System Information for S4FND component version.
    Affected if The installed S4FND version matches 1.02 or 1.03
  3. Confirm WebClient UI is deployed
    Check if the CRM WebClient UI application is active by accessing the SAPgui and navigating to BSP applications or checking transaction CRMD_WEB_UI for availability.
    Affected if The WebClient UI interface is accessible in the environment
  4. Verify external web access exists
    Check SAP ICM (Internet Communication Manager) configuration via transaction SMICM or review web dispatcher settings to determine if HTTP/HTTPS ports for WebClient UI are exposed externally.
    Affected if External HTTP/HTTPS access to CRM WebClient UI is enabled

Your environment is affected if any SAP WEBCUIF version 7.x/8.x or S4FND version 1.02/1.03 is installed AND the CRM WebClient UI web interface is accessible.

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 WEBCUIF and S4FND versions. Implement proper input validation and output encoding for all user-controlled data rendered in the CRM WebClient UI pages.

Recommended fix Moderate confidence
  1. Navigate to the SAP Launchpad (launchpad.support.sap.com) and search for Security Note associated with CVE-2023-24525
  2. Identify the relevant SAP Security Note number (typically contains the CVE reference)
  3. Download and apply the Security Note through SAP Transaction SNOTE or via SAP Maintenance Planner
  4. After applying the note, clear SAP buffers and restart relevant application servers if required
  5. Verify the patch has been applied by checking the SAP system version or using SAP Report SN_TEST_FOR_CVE if provided in the note

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
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-24525 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-24525 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