Skip to main content
VulnerabilityPublished

CVE-2025-42878: SAP Web Dispatcher and Internet Communication Manager (ICM) · Internal Asset Exposed to Unsafe Debug Access Level or State

Affects SAP Web Dispatcher and Internet Communication Manager (ICM)Source CVE Database V5

0

Not known to be exploited · CVSS 8.2 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:L/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Affected software

ProductAffectedFixed in
SAP_SE SAP Web Dispatcher and Internet Communication Manager (ICM)Affected
  • 7.53 – 9.16
6 affected builds
Fixed in–

AI-suggested

To mitigate CVE-2025-42878, European organizations should: 1) Immediately audit SAP Web Dispatcher and ICM configurations to identify and disable any internal testing or debug interfaces not intended for production use. 2) Apply SAP security notes and patches as soon as they become available, even though no patches are currently listed, monitoring SAP’s official channels for updates. 3) Implement strict network segmentation and access controls to limit exposure of SAP Web Dispatcher and ICM components to trusted internal networks only. 4) Employ robust monitoring and logging to detect unusual diagnostic interface access attempts or anomalous crafted requests. 5) Conduct regular security assessments and penetration tests focusing on SAP components to identify misconfigurations or exposures. 6) Train SAP administrators on secure configuration best practices, emphasizing the risks of enabling debug or test interfaces in production. 7) Consider deploying Web Application Firewalls (WAFs) with rules tailored to block suspicious requests targeting SAP diagnostic endpoints. 8) Maintain an incident response plan specific to SAP environments to quickly contain and remediate any exploitation attempts.

Description

SAP Web Dispatcher and ICM may expose internal testing interfaces that are not intended for production. If enabled, unauthenticated attackers could exploit them to access diagnostics, send crafted requests, or disrupt services. This vulnerability has a high impact on confidentiality, availability and low impact on integrity and of the application.

References

Community reviews

Loading reviews…