dbcve.org
Crm Webclient UiApplication · Sap

CVE-2024-22130

MEDIUM · 5.4 CVSS v3.1 Published 2024-02-13
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
Print preview option in SAP CRM WebClient UI - versions S4FND 102, S4FND 103, S4FND 104, S4FND 105, S4FND 106, S4FND 107, S4FND 108, WEBCUIF 700, WEBCUIF 701, WEBCUIF 730, WEBCUIF 731, WEBCUIF 746, WEBCUIF 747, WEBCUIF 748, WEBCUIF 800, WEBCUIF 801, does not sufficiently encode user-controlled inputs, resulting in Cross-Site Scripting vulnerability. An attacker with low privileges can cause limited impact to confidentiality and integrity of the appliaction data after successful exploitation.

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 the print preview feature of SAP CRM WebClient UI where user-controlled inputs are not properly encoded, allowing injection of malicious scripts that execute in the context of other users' sessions.

MitigationApply SAP security notes to address insufficient input encoding in the print preview component; implement proper output encoding for all user-controlled data rendered in the print preview functionality.

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
Crm Webclient UiApplication
Affected:= s4fnd_102= s4fnd_103= s4fnd_104= s4fnd_105= s4fnd_106= s4fnd_107= s4fnd_108= webcuif_700= webcuif_701= webcuif_730= webcuif_731= webcuif_746

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 CRM WebClient UI installation
    Check your SAP system for installed software components. Use transaction code SM37 or check system landscape documentation to confirm SAP CRM WebClient UI (webcuif) or S4FND component is deployed.
    Affected if SAP CRM WebClient UI or S4FND component is present in the system
  2. Verify installed version against affected ranges
    Check the installed version of webcuif or S4FND component in your SAP system. Use transaction code SM37, SPAM/SAINT, or check the system version information. Compare the version number to the affected list: s4fnd_102-108, webcuif_700, 701, 730, 731, 746.
    Affected if Installed version matches or falls within the listed affected versions (s4fnd_102 through s4fnd_108, or webcuif_700 through webcuif_746)
  3. Confirm print preview feature is in use
    Determine if the print preview functionality in SAP CRM WebClient UI is actively used or accessible in your environment. Check configuration settings or user access logs for CRM WebClient transactions that include printing capabilities.
    Affected if Print preview feature in SAP CRM WebClient UI is enabled and accessible to users
  4. Inspect custom modifications to print component
    Review any custom enhancements, modifications, or add-ons to the CRM WebClient UI print preview component. Check for custom BSP applications, enhancements, or modifications to the print preview framework in transaction SE80 or similar development tools.
    Affected if Custom code or modifications exist in the print preview component that could interact with user-controlled input

A system is affected if it runs SAP CRM WebClient UI with an affected version (s4fnd_102-108 or webcuif_700-746) AND has the print preview feature enabled, allowing unencoded user input to be rendered.

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 notes to address insufficient input encoding in the print preview component; implement proper output encoding for all user-controlled data rendered in the print preview functionality.

Recommended fix Moderate confidence

Upgrade to S4FND 106, S4FND 107, S4FND 108, or later WEBCUIF versions (700-801+) which contain the security fix

  1. 1. Verify your current SAP CRM WebClient UI version by checking the system information in SAP Logon or via transaction code SM37
  2. 2. Identify the relevant SAP Security Note for CVE-2024-22130 by searching SAP Support Portal (support.sap.com) using the CVE ID or checking SAP Security Notes
  3. 3. Download and apply the corresponding SAP Security Note patch for your S4FND or WEBCUIF version
  4. 4. After applying the patch, clear SAP buffer and restart the affected application server instances (transaction code SM37)
  5. 5. Verify the patch was successfully applied by checking the note implementation status in transaction code SNOTE
  6. 6. Test the print preview functionality in SAP CRM WebClient UI to confirm the XSS vulnerability is remediated
Caveat No significant breaking changes expected for this security patch; standard SAP regression testing recommended

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

Fix this in Crm Webclient Ui Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-22130 — 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-2024-22130 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