CVE-2022-27656
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 · uneditedThe Web administration UI of SAP Web Dispatcher and the Internet Communication Manager (ICM) does not sufficiently encode user-controlled inputs, 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 confidenceA reflected Cross-Site Scripting (XSS) vulnerability exists in the Web administration UI of SAP Web Dispatcher and Internet Communication Manager (ICM). The UI fails to properly encode user-controlled inputs, allowing attackers to inject malicious JavaScript code that executes in the context of an authenticated administrator's browser session.
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.22= 7.49= 7.53= 7.77= 7.81= 7.85= 7.86= 7.87= 8.04= 7.22= 7.22ext= 7.49= 7.53= 8.04= 7.22ext= 7.49= 7.53= 7.77= 7.81= 7.83= 7.85CVSS 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.1/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 Web Dispatcher or ICM is installedCheck for the presence of SAP Web Dispatcher by looking for the 'disp+work' executable or ICM-related processes. On Windows, check Program Files for SAP folder. On Unix, check /sapmnt/<SID>/exe or /usr/sap/<SID>/<instance> directories.Affected if The system has SAP Web Dispatcher or ICM components installed.
-
Check installed SAP Web Dispatcher versionRun the Web Dispatcher executable with version flag: ./disp+work -v or check the SAP Start Service (sapstartsrv) for version information via SAP Management Console or SAP MMC.Affected if The version matches exactly 7.22ext, 7.49, 7.53, 7.77, 7.81, 7.83, or 7.85.
-
Check installed SAP Netweaver ABAP Kernel versionExecute kernel version check: disp+work -version or use transaction SM51 in SAP GUI to view the kernel version, or check the kernel patch level in /usr/sap/<SID>/sys/exe/uc/<OS>/*.Affected if The kernel version is exactly 7.22, 7.22ext, 7.49, 7.53, 7.77, 7.81, 7.85, 7.86, 7.87, or 8.04.
-
Verify Web administration UI is accessibleAccess the SAP Web Dispatcher administration interface by navigating to https://<host>:<port>/sap/admin/public/index.html or checking if ports 50000-50010 (default Web Dispatcher admin ports) are open and responding.Affected if The Web administration UI is exposed and accessible over the network.
-
Review Web Dispatcher logs for XSS indicatorsExamine Web Dispatcher logs in the work directory for unusual URL parameters or script tags in HTTP requests. Look for entries containing patterns like <script>, javascript:, or encoded XSS payloads in the access logs.Affected if Logs contain suspicious requests with XSS payload patterns targeting the admin interface.
A system is affected if it runs SAP Web Dispatcher or Netweaver ABAP Kernel versions matching exactly 7.22 through 8.04 and has the Web administration UI exposed and accessible.
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 Notes to patch the vulnerability. Implement input validation and output encoding on all user-supplied data within the administration interface.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
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 locallyCheck whether your project pulls in CVE-2022-27656 — 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-2022-27656 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