CVE-2024-22128
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 NWBC for HTML - versions SAP_UI 754, SAP_UI 755, SAP_UI 756, SAP_UI 757, SAP_BASIS 700, SAP_BASIS 701, SAP_BASIS 702, SAP_BASIS 731, does not sufficiently encode user-controlled inputs, resulting in Cross-Site Scripting (XSS) vulnerability. An unauthenticated attacker can inject malicious javascript to cause limited impact to confidentiality and integrity of the application 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 · moderate confidenceSAP NetWeaver Business Client (NWBC) for HTML fails to properly encode user-controlled inputs in multiple SAP_UI and SAP_BASIS versions, allowing unauthenticated attackers to inject malicious JavaScript via cross-site scripting (XSS). Successful exploitation enables limited compromise of confidentiality and integrity through execution of attacker-controlled scripts in victim browsers.
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= sap_basis_700= sap_basis_701= sap_basis_702= sap_basis_731= sap_ui_754= sap_ui_755= sap_ui_756= sap_ui_757= sap_ui_758CVSS 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 SAP NetWeaver Business Client for HTML installationCheck if NWBC for HTML is installed in your SAP system by reviewing SAP system components via transaction SM37 or by checking the SAP system landscapeAffected if NWBC for HTML is deployed and active in the environment
-
Determine SAP_BASIS versionExecute transaction code SMIF or use transaction SMICM to view the installed SAP_BASIS version, or run SAP command 'sapcontrol -nr <instance> -function GetVersionInfo'Affected if The installed SAP_BASIS version matches one of these: 700, 701, 702, or 731
-
Determine SAP_UI versionExecute transaction code SMICM or check via SAP system information panel to identify the SAP_UI component version numberAffected if The installed SAP_UI version matches one of these: 754, 755, 756, 757, or 758
-
Verify NWBC HTML mode is enabledCheck NWBC configuration via transaction NWBC or system settings to confirm HTML mode rendering is active for end usersAffected if NWBC is configured to render in HTML mode, enabling the vulnerable code path
Your environment is affected if SAP NWBC for HTML is running with SAP_BASIS versions 700-702 or 731, or SAP_UI versions 754-758, and HTML mode rendering is enabled.
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 SAP security patches for affected SAP_UI and SAP_BASIS versions; validate and encode all user-supplied inputs before rendering in HTML output.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-22128 — 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-2024-22128 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