dbcve.org
Netweaver Application Server AbapApplication · Sap

CVE-2022-39799

MEDIUM · 6.1 CVSS v3.1 Published 2022-09-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
An attacker with no prior authentication could craft and send malicious script to SAP GUI for HTML within Fiori Launchpad, resulting in reflected cross-site scripting attack. This could lead to stealing session information and impersonating the affected user.

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 confidence

This is a reflected cross-site scripting (XSS) vulnerability in SAP GUI for HTML within the Fiori Launchpad. An unauthenticated attacker can inject malicious JavaScript via crafted requests that get reflected back in the HTTP response, allowing session cookie theft and user impersonation.

MitigationApply the relevant SAP security patch (refer to SAP Security Note 3268706) to remediate the input validation flaw in Fiori Launchpad, then validate via manual penetration testing that XSS payloads are no longer executable.

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
Netweaver Application Server AbapApplication
Affected:= 7.54= 7.81= 7.85= 7.89= kernel_7.77

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Fiori Launchpad is enabled
    Access the Fiori Launchpad URL (typically /sap/bc/ui5_ui5/ui2/ushell or /sap/fiori) via browser or check SAP Gateway configuration for UI5/USHELL components
    Affected if Fiori Launchpad is accessible and the UI5/USHELL components are deployed
  2. Identify SAP NetWeaver ABAP version
    Execute transaction SM37 and check system version, or use SAP MII version checker, or inspect SAP note 11208 for kernel version. Also check /sap/adminInfo endpoint if available
    Affected if Version matches 7.54, 7.81, 7.85, 7.89 or kernel_7.77 (compare your installed version to these specific affected ranges)
  3. Verify SAP GUI for HTML is active
    Check if /sap/bc/gui/sap/its/webgui or /sap/bc/htmlb and related ITS services are running via transaction SICF
    Affected if SAP GUI for HTML (ITS) is active and exposed via Fiori Launchpad
  4. Test for reflected XSS in Fiori Launchpad
    Send a crafted HTTP GET request to the Fiori Launchpad with a test XSS payload in a parameter (such as ?~token=<script>alert(1)</script> or in navigation parameters) and inspect the HTTP response for unsanitized reflection of the payload
    Affected if The payload is reflected verbatim in the response without encoding or sanitization

User is affected if Fiori Launchpad with SAP GUI for HTML is enabled AND the NetWeaver version matches 7.54, 7.81, 7.85, 7.89, or kernel_7.77 AND reflected XSS is confirmed via manual testing.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant SAP security patch (refer to SAP Security Note 3268706) to remediate the input validation flaw in Fiori Launchpad, then validate via manual penetration testing that XSS payloads are no longer executable.

Recommended fix Moderate confidence

SAP NetWeaver ABAP version > 7.89 (specific version per SAP Security Note)

  1. 1. Review the SAP Security Note for CVE-2022-39799 in the SAP Support Portal (launchpad.support.sap.com) to obtain the specific patch or correction instructions.
  2. 2. Identify the current SAP NetWeaver ABAP version by executing transaction SM51 or checking the system profile.
  3. 3. Plan an upgrade to a version higher than 7.89, which would contain the security fix for this reflected XSS vulnerability.
  4. 4. Before applying to production, test the patch/upgrade in a development or staging system to verify the fix and check for regressions.
  5. 5. Schedule maintenance window and apply the correction following SAP's standard upgrade procedures.
  6. 6. After applying, validate the fix by attempting to confirm the XSS vulnerability is mitigated in the Fiori Launchpad SAP GUI for HTML component.
Caveat SAP system upgrades may require regression testing, ABAP code adjustments, and compatibility verification with connected systems; review SAP Notes for any dependent corrections

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Netweaver Application Server Abap Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-39799 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-39799 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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