VulnerabilityPublished 14 Oct 2025

CVE-2025-42903: SAP Financial Service Claims Management · Observable Response Discrepancy

Affects SAP Financial Service Claims ManagementSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

4.3Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 26% 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 14 Oct 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 26 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, 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_SE SAP Financial Service Claims Management	Affected 108 – 806 5 affected builds	Fixed in–

AI-suggested

To mitigate this vulnerability, organizations should implement strict access controls on the RFC function ICL_USER_GET_NAME_AND_ADDRESS, limiting its use to authorized personnel and systems only. Network segmentation should be employed to restrict access to SAP Financial Service Claims Management components. Monitoring and logging of RFC calls should be enhanced to detect unusual or repeated queries indicative of user enumeration attempts. Organizations should apply SAP security notes and patches promptly once available. Additionally, employing SAP’s security audit tools to review permissions and function usage can help identify and remediate excessive privileges. Training staff to recognize and report suspicious activity related to SAP systems is also recommended. Finally, organizations should review and update their incident response plans to include scenarios involving reconnaissance and data disclosure vulnerabilities.

Description

CVE-2025-42903 is a medium severity vulnerability in SAP Financial Service Claims Management affecting multiple versions. It involves an observable response discrepancy in the RFC function ICL_USER_GET_NAME_AND_ADDRESS, which can be exploited for user enumeration and limited disclosure of personal data. The vulnerability impacts confidentiality with no effect on integrity or availability and requires low privileges but no user interaction. There are no known exploits in the wild, and no patches have been published yet. The affected SAP versions include INSURANCE 803 through 806 and S4CEXT 107 through 109. European organizations using these SAP modules, especially in insurance and financial sectors, could face targeted reconnaissance attempts. Mitigation involves restricting access to the vulnerable RFC function, monitoring for unusual query patterns, and applying SAP security best practices. Countries with significant SAP Financial Services deployments and strong insurance sectors, such as Germany, France, and the UK, are most likely to be affected. The vulnerability’s CVSS score is 4.3, reflecting a medium severity due to limited confidentiality impact and ease of exploitation with privileges.

Impact

For European organizations, especially those in the insurance and financial sectors using SAP Financial Service Claims Management, this vulnerability poses a risk of user enumeration and limited personal data exposure. While the confidentiality impact is low, the information gained could aid attackers in crafting targeted phishing campaigns or further attacks. There is no direct impact on system integrity or availability, so operational disruption is unlikely. However, the exposure of personal data could lead to regulatory compliance issues under GDPR, potentially resulting in fines or reputational damage. The vulnerability could be exploited by malicious insiders or external attackers who have gained low-level access to the network. Given the widespread use of SAP in Europe’s financial services industry, the vulnerability could be leveraged for reconnaissance in preparation for more severe attacks.

Summary

CVE-2025-42903 identifies a vulnerability in SAP Financial Service Claims Management, specifically within the remote function call (RFC) ICL_USER_GET_NAME_AND_ADDRESS. This function exhibits an observable response discrepancy that allows an attacker with low-level privileges to perform user enumeration and potentially disclose limited personal data. The vulnerability falls under CWE-204 (Observable Response Discrepancy), where differences in system responses can be used to infer sensitive information. The affected SAP versions include INSURANCE 803 to 806 and S4CEXT 107 to 109. Exploitation requires network access and low privileges but no user interaction, making it feasible for insiders or attackers with limited access to gather intelligence. The impact is confined to confidentiality, with no integrity or availability consequences. No public exploits or patches are currently available, indicating the vulnerability is newly disclosed and not yet actively exploited. The CVSS 3.1 score of 4.3 reflects the medium severity, considering the ease of exploitation but limited impact scope. The vulnerability is particularly relevant for organizations relying on SAP Financial Service Claims Management modules, as it could facilitate targeted reconnaissance or social engineering by revealing user existence and partial personal data.

CWE-204Observable Response Discrepancy (opens in a new tab)
Base weakness
The product provides different responses to incoming requests in a way that reveals internal state information to an unauthorized actor outside of the intended control sphere.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
Implementation
Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended).
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
ICMP IP Total Length Field Probe (opens in a new tab)
ICMP IP 'ID' Field Error Message Probe (opens in a new tab)
Application Fingerprinting (opens in a new tab)
System Footprinting (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 21 Oct 2025, 12:01 UTC

WeaknessesCWE-204

Technical details

References

Community reviews

Related threats