CVE-2026-24311: SAP Customer Checkout 2.0 · Cleartext Storage of Sensitive Information
Affects SAP Customer Checkout 2.0Source CVE Database V5
Not known to be exploited · CVSS 5.6 Medium.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.09% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:P/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 10 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SAP_SESAP Customer Checkout 2.0 | Affected
| Fixed in– |
AI-suggested
To mitigate this vulnerability, organizations should implement the following specific measures: 1) Restrict and monitor access to systems running SAP Customer Checkout 2.0 to prevent unauthorized local access, ensuring only trusted administrators have high-level privileges. 2) Enhance local data protection by applying additional encryption layers or using secure storage mechanisms that do not rely on reversible protection. 3) Implement strict validation and integrity checks on all locally stored operational data, especially before system startup, to detect and prevent unauthorized modifications. 4) Employ endpoint security solutions to detect suspicious activities related to file access or modification within the SAP Customer Checkout environment. 5) Conduct regular audits and integrity verification of configuration and operational data files. 6) Educate users and administrators about the risks of local data manipulation and enforce policies to minimize user-initiated risky actions. 7) Monitor SAP security advisories for patches or updates addressing this vulnerability and apply them promptly once available. 8) Consider network segmentation and isolation of systems running SAP Customer Checkout to limit exposure to lateral movement.
Description
The SAP Customer Checkout application exhibits certain design characteristics that involve locally storing operational data using reversible protection mechanisms. Access to this data, combined with user?initiated interaction, may allow modifications to occur without validation. Such changes could affect system behaviour during startup, resulting in a high impact on the application's confidentiality and integrity, with a low impact on availability.