VulnerabilityPublished 24 Feb 2026

CVE-2026-24314: SAP_SE S/4HANA (Manage Payment Media) · Exposure of Sensitive System Information to an Unauthorized Control Sphere

Affects SAP_SE S/4HANA (Manage Payment Media)Source CVE Database V5

Compare

Not known to be exploited · CVSS 4.3 Medium.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score

4.3Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
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: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
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 24 Feb 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.

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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity 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

Affected software

Product	Affected	Fixed in
SAP_SES/4HANA (Manage Payment Media)	Affected 700 – 902 5 affected builds	Fixed in–

AI-suggested

To mitigate CVE-2026-24314, organizations should take the following specific actions: 1) Immediately review and tighten access controls and user privileges within the SAP S/4HANA Manage Payment Media module to ensure the principle of least privilege is enforced. 2) Implement robust monitoring and auditing of access to payment media data to detect unusual or unauthorized access patterns promptly. 3) Employ multi-factor authentication (MFA) for all users accessing SAP S/4HANA systems to reduce the risk of credential compromise. 4) Segregate network access to SAP systems, limiting exposure to trusted networks and users only. 5) Stay alert for SAP security advisories and apply patches or updates as soon as they become available, even though no patches are currently linked. 6) Conduct regular security awareness training for users with SAP access to minimize insider threats and credential misuse. 7) Consider deploying data loss prevention (DLP) solutions to monitor and control sensitive data flows related to payment media. These targeted measures go beyond generic advice by focusing on access control, monitoring, and credential protection specific to the affected SAP module and its sensitive data.

Description

Under certain conditions SAP S/4HANA (Manage Payment Media) allows an authenticated attacker to access information which would otherwise be restricted. This could cause low impact on confidentiality of the application while integrity and availability are not impacted.

Impact

The primary impact of CVE-2026-24314 is the unauthorized disclosure of sensitive system information within the SAP S/4HANA Manage Payment Media module. This can lead to confidentiality breaches involving payment processing data, which may include transaction details, payment instructions, or other financial metadata. While integrity and availability remain unaffected, the exposure of sensitive information can facilitate further targeted attacks, social engineering, or fraud attempts. Organizations relying on SAP S/4HANA for critical financial operations could face regulatory compliance issues, reputational damage, and potential financial losses if sensitive data is leaked. The requirement for authenticated access reduces the risk from external attackers but does not eliminate threats from insiders or attackers who have obtained valid credentials. Given the widespread use of SAP S/4HANA in large enterprises and financial institutions globally, the vulnerability could have a broad impact if exploited at scale.

CWE-497Exposure of Sensitive System Information to an Unauthorized Control Sphere (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does.
Architecture and Design · Implementation
Production applications should never use methods that generate internal details such as stack traces and error messages unless that information is directly committed to a log that is not viewable by the end user.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V14.3.2 (opens in a new tab)
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
Attack patterns
Web Application Fingerprinting (opens in a new tab)
System Location Discovery (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

Affected software

Description

AI analysisMachine-generated, updated 24 Feb 2026, 06:01 UTC

WeaknessesCWE-497

Technical details

References

Community reviews

Related threats