CVE-2023-27499
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 GUI for HTML - versions KERNEL 7.22, 7.53, 7.54, 7.77, 7.81, 7.85, 7.89, 7.91, KRNL64UC, 7.22, 7.22EXT, KRNL64UC 7.22, 7.22EXT does not sufficiently encode user-controlled inputs, resulting in a reflected Cross-Site Scripting (XSS) vulnerability. An attacker could craft a malicious URL and lure the victim to click, the script supplied by the attacker will execute in the victim user's browser. The information from the victim's web browser can either be modified or read and sent to the attacker.
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 confidenceA reflected Cross-Site Scripting (XSS) vulnerability in SAP GUI for HTML exists due to insufficient encoding of user-controlled inputs. Attackers can craft malicious URLs that, when clicked by victims, execute arbitrary JavaScript in the victims' browsers, allowing attackers to read or modify browser-based information.
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.22ext= 7.22= 7.53= 7.54= 7.77= 7.81= 7.85= 7.89= 7.91= krnl64uc= krnl64uc_7.22CVSS 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 versionExecute transaction SM51 in SAP GUI or use SAP kernel binaries (disp+work -version) to retrieve the Netweaver release version. Check the kernel version using 'sapkernel -v' or reviewing the kernel patch level.Affected if The installed Netweaver version matches 7.22, 7.53, 7.54, 7.77, 7.81, 7.85, 7.89, or 7.91, or the kernel version is krnl64uc or krnl64uc_7.22
-
Confirm SAP GUI for HTML is activeExecute transaction SICF and navigate to the SAP GUI for HTML service path (typically /sap/bc/gui/sap/its/webgui or /sap/bc/webgui). Verify the service status is active.Affected if The SAP GUI for HTML (WebGUI) ICF service is activated and accessible via HTTP/HTTPS
-
Verify external-facing configurationReview transaction SMICM ( ICM Monitor) to check if HTTP/HTTPS ports are open externally. Use transaction SRT to check if WebGUI is exposed via SAP Router or directly accessible.Affected if The WebGUI service is externally accessible without proper network restrictions or SAP Router protection
-
Check for recent security patchesReview SAP Note 3294569 (or related security notes for CVE-2023-27499) to identify if the specific kernel patches have been applied. Use transaction SNOTE to review applied security corrections.Affected if No relevant security patches for this XSS vulnerability have been applied to the system
A system is affected if it runs any of the specified SAP Netweaver versions (7.22, 7.53, 7.54, 7.77, 7.81, 7.85, 7.89, 7.91 or krnl64uc variants) with SAP GUI for HTML service 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 kernel security patches for the affected versions (7.22, 7.53, 7.54, 7.77, 7.81, 7.85, 7.89, 7.91 and related KRNL64UC versions). Implement output encoding and input validation as defense-in-depth measures.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-27499 — 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-27499 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