CVE-2023-33991
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 UI5 Variant Management - versions SAP_UI 750, SAP_UI 754, SAP_UI 755, SAP_UI 756, SAP_UI 757, UI_700 200, does not sufficiently encode user-controlled inputs on reading data from the server, resulting in Stored Cross-Site Scripting (Stored XSS) vulnerability. After successful exploitation, an attacker with user level access can cause high impact on confidentiality, modify some information and can cause unavailability of the application at user level.
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 confidenceSAP UI5 Variant Management versions 750, 754-757 and UI_700 200 contains a stored XSS vulnerability where user-controlled inputs retrieved from the server are not sufficiently encoded, allowing authenticated users to inject malicious scripts that execute in other users' browsers when variant data is displayed.
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= 700= 750= 754= 755= 756= 757CVSS 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
- High
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:L
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 UI5 framework version in useCheck the UI5 bootstrap file or the application's manifest.json for the ui5 version parameter. This is typically found in the bootstrap script tag (src attribute pointing to sap-ui-core.js) or in the app descriptor under the sap.ui5 dependencies section.Affected if The version listed matches 700, 750, 754, 755, 756, or 757.
-
Verify Variant Management component is deployedSearch the application codebase for references to sap.ui.comp.variantmanagement or related variant management controls. Check if the application uses SmartVariantManagement or VariantManagement controls.Affected if The Variant Management module is present in the deployed application.
-
Inspect how variant data is handled in controllersExamine the controller logic that handles variant save and load operations. Look for code paths where user input is accepted for variant names, descriptions, or variant data fields.Affected if User-controlled data is accepted and stored for variant fields without visible sanitization.
-
Examine variant rendering templates for encodingReview XML views or fragment files that render variant information. Look for the use of data binding expressions and check if text content is being rendered through text nodes or HTML-aware bindings.Affected if The variant display templates do not use HTML escaping mechanisms or output encoding for user-supplied variant data.
-
Check for custom variant implementationsReview any custom extensions or modifications to the standard VariantManagement control. Look for overrides of methods like getVariantData or custom format calls.Affected if Custom code handles variant data without applying output encoding.
A user is affected if they run any of the listed UI5 versions (700, 750, 754-757) AND use the Variant Management feature where unencoded user input can be stored and displayed to other users.
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 · scopedApply SAP security patches for CVE-2023-33991 which implement proper output encoding of user-controlled data in the Variant Management component, and verify the fix through stored XSS testing.
SAP_UI 758 or higher (or latest available SAP_UI stack with the CVE-2023-33991 patch)
- 1. Identify the current SAP_UI version running in your system using SAP transaction SMICM or by checking the SAP Fiori launchpad configuration.
- 2. Download and install the latest available SAP_UI stack or support package that includes the security fix for CVE-2023-33991.
- 3. After applying the update, verify the fix by confirming that user-controlled inputs in the Variant Management feature are properly encoded.
- 4. Test the Variant Management functionality in your UI5 applications to ensure the XSS fix does not break existing features.
- 5. Clear any cached server-side data and restart the SAP UI5 services to ensure the patched code is active.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-33991 — 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-2023-33991 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