CVE-2024-27902
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 · uneditedApplications based on SAP GUI for HTML in SAP NetWeaver AS ABAP - versions 7.89, 7.93, do not sufficiently encode user-controlled inputs, resulting in Cross-Site Scripting (XSS) vulnerability. A successful attack can allow a malicious attacker to access and modify data through their ability to execute code in a user’s browser. There is no impact on the availability of the system
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 confidenceCross-Site Scripting (XSS) vulnerability in SAP GUI for HTML within SAP NetWeaver AS ABAP versions 7.89 and 7.93. The application fails to sufficiently encode user-controlled inputs, allowing attackers to inject malicious scripts that execute in users' 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_ui_7.89= sap_ui_7.93CVSS 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.
-
Verify SAP NetWeaver ABAP versionAccess SAP transaction SM51 to display the SAP System version, or use SAP transaction SWDA to check the kernel and component versions. Look specifically for the SAP_UI component version.Affected if The SAP_UI component version is 7.89 or 7.93, indicating the system is running an affected version.
-
Confirm SAP GUI for HTML is enabledCheck if the ICM (Internet Communication Manager) and ICF (Internet Communication Framework) services are active for SAP GUI for HTML. Use transaction SICF and verify the /sap/bc/gui/sap/its tree is active.Affected if SAP GUI for HTML is accessible and the system is running an affected SAP_UI version (7.89 or 7.93).
-
Check SAP_UI component patch levelUse transaction SAAB or check the SAP Solution Manager to examine the installed Support Package level for the SAP_UI component. Compare the exact version number against the affected ranges.Affected if The installed SAP_UI version matches exactly 7.89 or 7.93 without additional patches applied.
-
Review ICF handler configurationUse transaction SICF to inspect the ICF handlers configured for the SAP GUI for HTML service paths. Look for any custom or third-party handlers that may affect input processing.Affected if Custom ICF handlers are active on a system with SAP_UI versions 7.89 or 7.93.
A system is affected if it runs SAP NetWeaver AS ABAP with SAP_UI component versions exactly 7.89 or 7.93 and has SAP GUI for HTML enabled 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 address the XSS vulnerability. For SAP NetWeaver AS ABAP, this involves implementing SAP-provided patches and ensuring proper input validation and output encoding are in place.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-27902 — 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-27902 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