Vulnerabilities

Vulnerability · CVE-2025-42903

A vulnerability in SAP Financial Service Claims Management RFC function ICL_USER_GET_NAME_AND_ADDRESS allows user enumeration and potential disclosure of personal data through resp

Published Oct 14, 2025 · catalog updated Oct 14, 2025 · SAP_SE SAP Financial Service Claims Management

Last checked Nov 1, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2025-42903. EPSS is 0.34%. Act only if a listed version of SAP_SE SAP Financial Service Claims Management is installed.

Gaps on this record

  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium4.3
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.34%
Remediation
Advisory link
Affected products
vendor SAP_SE SAP Financial Service Claims Management 804

A vulnerability in SAP Financial Service Claims Management RFC function ICL_USER_GET_NAME_AND_ADDRESS allows user enumeration and potential disclosure of personal data through response discrepancies, causing low impact on confidentiality with no impact on integrity or availability.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • vendor SAP_SE SAP Financial Service Claims Management 804804

How to fix CVE-2025-42903

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2025-42903. EPSS is 0.34%. Act only if a listed version of SAP_SE SAP Financial Service Claims Management is installed.

Which versions are affected?

Compare what you have installed with SAP_SE SAP Financial Service Claims Management 804 804. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 0.34%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 14, 2025 · EUVD

    Detected

    A vulnerability in SAP Financial Service Claims Management RFC function ICL_USER_GET_NAME_AND_ADDRESS allows user enumeration and potential disclosure of personal data through response discrepancies, causing low impact on confidentiality with no impact on integrity or availability.

  2. Oct 14, 2025 · EUVD

    Updated

    A vulnerability in SAP Financial Service Claims Management RFC function ICL_USER_GET_NAME_AND_ADDRESS allows user enumeration and potential disclosure of personal data through response discrepancies, causing low impact on confidentiality with no impact on integrity or availability.

Sources

  • CVE.orgVulnerability recordCVE-2025-42903

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2025-42903

    30-day exploitation probability 0.34%

    first.org
  • EUVDVulnerability recordEUVD-2025-34124

    A vulnerability in SAP Financial Service Claims Management RFC function ICL_USER_GET_NAME_AND_ADDRESS allows user enumeration and potential disclosure of personal data through response discrepancies, causing low impact on confidentiality with no impact on integrity or availabilit

    euvd.enisa.europa.eu

References

Freshness

Last verified in this catalog Nov 1, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • CVE.orgOct 23, 2026
  • FIRST EPSSOct 23, 2026
  • EUVDOct 23, 2026
CVE-2025-42903: SAP Financial Service Cl… CVSS 4.3 · ZeroDay Findings