dbcve.org
Gui For WindowsApplication · Sap

CVE-2021-40503

HIGH · 7.8 CVSS v3.1 Published 2021-11-10
Fix available
A fix is available. Upgrade to 7.60 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 information disclosure vulnerability exists in SAP GUI for Windows - versions < 7.60 PL13, 7.70 PL4, which allows an attacker with sufficient privileges on the local client-side PC to obtain an equivalent of the user’s password. With this highly sensitive data leaked, the attacker would be able to logon to the backend system the SAP GUI for Windows was connected to and launch further attacks depending on the authorizations of the 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 · high confidence

A local information disclosure vulnerability in SAP GUI for Windows allows an attacker with sufficient local client-side privileges to obtain password-equivalent credentials, enabling unauthorized backend system access. The vulnerability exists in versions prior to 7.60 PL13 and 7.70 PL4.

MitigationUpgrade SAP GUI for Windows to version 7.60 PL13, 7.70 PL4, or higher. Verify that credential storage mechanisms are properly protected after patching.

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
Gui For WindowsApplication
Affected:< 7.60= 7.60= 7.70

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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. Identify installed SAP GUI version
    Open SAP Logon, click 'About SAP Logon' or check Help > About. Alternatively, locate sapgui.exe in the SAP GUI installation directory (commonly C:\Program Files\SAP\SAPGUI) and view file properties to see the version. You can also check the Windows Registry under HKLM\SOFTWARE\SAP\SAPGUI\CurrentVersion for the Version value.
    Affected if The version displayed is any release prior to 7.60, or is exactly 7.60 or 7.70 (without the respective PL13 or PL4 patch level).
  2. Confirm patch level for version 7.60
    If the version shows 7.60, verify the Patch Level (PL) by viewing the same version information source used in the previous step. The full version string typically appears as something like '7.60 PL13' or '7.60.0.13'.
    Affected if The patch level is below PL13 (for example, PL0 through PL12) or the patch level information is missing entirely.
  3. Confirm patch level for version 7.70
    If the version shows 7.70, verify the Patch Level (PL) by viewing the version information. Check if it shows '7.70 PL4' or higher.
    Affected if The patch level is below PL4 (for example, PL0 through PL3) or the patch level information is missing entirely.
  4. Check for stored SAP credentials
    Review whether the system has saved user credentials for SAP connections. In SAP Logon, go to Options > Security Settings > Secure Storage or check if 'Save password' has been enabled for any SAP system entries in the connection list.
    Affected if Saved credentials exist in SAP Logon's secure storage and the installed SAP GUI version falls within the affected version range.

Your environment is affected if the installed SAP GUI for Windows version is any release prior to 7.60, or is exactly 7.60 with patch level below PL13, or is exactly 7.70 with patch level below PL4, and you have stored credentials in the application.

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
Upgrade available Upgrade to 7.60 or later
Fixed in 7.60
Interim mitigation

Upgrade SAP GUI for Windows to version 7.60 PL13, 7.70 PL4, or higher. Verify that credential storage mechanisms are properly protected after patching.

Recommended fix High confidence

SAP GUI for Windows 7.60 PL13 or 7.70 PL4 (or later supported release)

  1. Identify the currently installed SAP GUI for Windows version (Help > About SAP GUI)
  2. Access the SAP Support Portal (launchpad.support.sap.com) and navigate to the SAP GUI for Windows downloads
  3. Download the fixed version: SAP GUI for Windows 7.60 PL13 or 7.70 PL4 (or a later supported version)
  4. Close all SAP GUI sessions and any running SAP-related processes
  5. Run the SAP GUI installer with administrator privileges
  6. Follow the on-screen installation wizard prompts to complete the upgrade
  7. Restart the computer if prompted by the installer
  8. Launch SAP GUI and verify the new version is installed (Help > About SAP GUI)
Caveat Review SAP GUI compatibility notes for your specific SAP ERP/Backend version before upgrading, as minor GUI releases may introduce subtle UI or interaction changes

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

Fix this in Gui For Windows Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,488.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-40503 — 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-2021-40503 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