CVE-2025-42979VulnerabilityPublished 8 Jul 2025

CVE-2025-42979: SAP GUI for Windows · Insecure Storage of Sensitive Information

Affects SAP GUI for WindowsSource CVE Database V5

Not known to be exploited · CVSS 5.6 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.6Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Local
Attack Complexity: High
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate this vulnerability, European organizations should implement the following specific measures: 1) Restrict access to user workstations and enforce strict endpoint security controls, including strong authentication and session locking, to prevent unauthorized local access to the Windows registry. 2) Regularly audit and monitor access to the Windows registry hives where SAP credentials are stored to detect suspicious activities. 3) Employ application whitelisting and endpoint detection and response (EDR) solutions to detect and block unauthorized attempts to access or extract registry data. 4) Where possible, disable or limit the use of the GuiXT application or the storage of RFC credentials on client machines, opting instead for more secure authentication methods such as single sign-on or token-based authentication. 5) Educate users about the risks of credential exposure and the importance of securing their workstations. 6) Monitor SAP GUI client updates and apply patches promptly once SAP releases a fix for this vulnerability. 7) Consider implementing additional encryption or credential vaulting solutions at the endpoint to protect stored credentials beyond the native SAP GUI mechanisms. 8) Review and tighten SAP user permissions to minimize the impact if credentials are compromised.

Description

The GuiXT application, which is integrated with SAP GUI for Windows, uses obfuscation algorithms instead of secure symmetric ciphers for storing the credentials of an RFC user on the client PC. This leads to a high impact on confidentiality because any attacker who gains access to the user hive of this user�s windows registry could recreate the original password. There is no impact on integrity or availability of the application

Impact

For European organizations using SAP GUI for Windows with the GuiXT application, this vulnerability poses a significant risk to the confidentiality of RFC user credentials. Since SAP systems are widely used in Europe across various sectors including manufacturing, finance, and public administration, the exposure of these credentials could allow attackers to impersonate legitimate users and execute unauthorized remote function calls. This could lead to unauthorized data access, data exfiltration, or manipulation of business-critical processes. Although the vulnerability does not directly impact system integrity or availability, the compromise of credentials can be a stepping stone for further attacks within the enterprise network. The requirement for local access limits the attack vector to insiders or attackers who have already compromised a user's workstation. However, given the high value of SAP credentials, even limited access can have severe consequences. European organizations with less stringent endpoint security or those that allow shared or poorly controlled user workstations are at higher risk. Additionally, regulatory frameworks such as GDPR impose strict requirements on protecting personal and sensitive data, so a breach resulting from this vulnerability could lead to compliance violations and financial penalties.

CWE-922Insecure Storage of Sensitive Information (opens in a new tab)
Class weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product stores sensitive information without properly limiting read or write access by unauthorized actors.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.6 (opens in a new tab)
V8.2.3 (opens in a new tab)
V8.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 8 Jul 2025, 00:56 UTC

WeaknessesCWE-922

Technical details

References

Community reviews

Related threats