CVE-2022-28770
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 · uneditedDue to insufficient input validation, SAPUI5 library(vbm) - versions 750, 753, 754, 755, 75, allows an unauthenticated attacker to inject a script into the URL and execute code. On successful exploitation, an attacker can view or modify information causing a limited impact on confidentiality and integrity 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 · high confidenceThis is a reflected Cross-Site Scripting (XSS) vulnerability in SAPUI5's vbm library due to insufficient input validation. An unauthenticated attacker can inject malicious JavaScript into the URL parameter, which gets executed in the victim's browser when they access the crafted URL, allowing viewing or modification of application data.
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= 200= 750= 753= 754= 755= 756CVSS 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 the installed SAPUI5 versionLocate the SAPUI5 bootstrap script (typically sap-ui-core.js or similar) and check the version identifier in the file path or the version comment/constant within the script. Also check the SAPUI5 core's getVersion() method if accessible in your environment.Affected if The version number matches 200, 750, 753, 754, 755, or 756.
-
Determine if the vbm library is loadedInspect the HTML source or network requests of your SAPUI5 application for script tags or module imports referencing the vbm library (look for paths containing '/vbm/' or 'vbm.js').Affected if The vbm library (visual business library) is loaded and accessible in your application.
-
Review web server access logs for vbm URL parametersSearch your web server (IIS, Apache, SAP ICM) access logs for requests containing '/sap/bc/ui5_ui5/' paths with 'vbm' in the URL, and inspect any query parameters passed to these endpoints.Affected if Requests with user-supplied parameters are being processed by the vbm library without sanitization.
-
Inspect the vbm library's input handling codeLocate the vbm library JavaScript file in your SAPUI5 distribution and examine how URL parameters are processed (look for code handling location.search, URL parameters, or DOM manipulation of parameter values).Affected if The code directly uses URL parameter values in DOM operations (such as innerHTML, document.write, or event handlers) without encoding or validation.
-
Check WAF or proxy logs for XSS attempts targeting vbmReview your web application firewall, reverse proxy, or application gateway logs for any blocked requests with XSS payloads in URL parameters directed at vbm-related endpoints.Affected if Malicious payloads are being detected and blocked, indicating active targeting of this vulnerability.
You are affected if your SAPUI5 version is exactly 200, 750, 753, 754, 755, or 756 AND the vbm library is loaded in your application, allowing reflected XSS via URL parameters.
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.
dbcve · scopedOrganizations should update to a patched version of SAPUI5 when available from SAP. Until then, implement web application firewall (WAF) rules to detect and block XSS payloads in URL parameters, and educate users about not clicking suspicious links.
SAPUI5 version 755 or latest stable release
- Identify the current SAPUI5 version deployed in your application by checking the bootstrap script or library references
- Access the SAP Support Portal (launchpad.support.sap.com) and search for Security Note 3222603 or CVE-2022-28770 to obtain the specific patch information
- Upgrade SAPUI5 library to version 755 or higher (or the latest available version that includes the fix)
- After upgrading, clear browser cache and test to confirm the URL-based XSS vulnerability is remediated
- Deploy the updated SAPUI5 library to production environments
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28770 — 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-28770 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