CVE-2018-2364
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 · uneditedSAP CRM WebClient UI 7.01, 7.31, 7.46, 7.47, 7.48, 8.00, 8.01, S4FND 1.02, does not sufficiently validate and/or encode hidden fields, resulting in Cross-Site Scripting (XSS) vulnerability.
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 confidenceSAP CRM WebClient UI fails to properly validate and encode hidden form fields, allowing injection of malicious JavaScript that executes when those field values are rendered in the browser without sanitization. This is a stored XSS vulnerability affecting multiple versions from 7.01 through 8.01 and S4FND 1.02.
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= 7.01= 7.31= 7.46= 7.47= 7.48= 8.00= 8.01= 1.02CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if SAP CRM WebClient UI is presentAccess the SAP system and use transaction code SM37 or system information commands (sapcontrol -getprocesslist) to confirm the WebClient UI component is installed and runningAffected if The WebClient UI component is not found or not installed, the system is not affected via this vector
-
Determine the installed SAP CRM versionUse SAP transaction code SM37 or execute: sapcontrol -nr <instance> -function GetSystemInstance to retrieve the SAP CRM WebClient UI version number from the systemAffected if The installed version matches 7.01, 7.31, 7.46, 7.47, 7.48, 8.00, 8.01 or S4FND 1.02 as listed in the affected versions
-
Check if WebClient UI is enabled and accessibleVerify the WebClient UI HTTP/HTTPS endpoints are active by reviewing SAP ICM (Internet Communication Manager) configuration via transaction SMICM or by attempting to access the WebClient UI login pageAffected if The WebClient UI is enabled and accessible, the application is exposed to the vulnerability
-
Identify hidden form field usage in WebClient UIInspect the WebClient UI application configuration and HTML response from the UI pages to locate hidden form fields that may contain user-supplied dataAffected if Hidden form fields exist in the WebClient UI that accept and render user-controlled values without proper encoding
A system is affected if it runs SAP CRM WebClient UI versions 7.01 through 8.01 or S4FND 1.02, has the WebClient UI component enabled, and contains hidden form fields that accept user input without sanitization.
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 the relevant SAP security patch for CVE-2018-2364 and implement proper output encoding for all hidden field values in the WebClient UI.
- Consultation6.0 h
- Implementation12.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-2364 — 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-2018-2364 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