SAP NetWeaver Improper Neutralization of Special Elements in Data Query Logic Vulnerability

🚨SEVERITY: MEDIUM — CVSS 6.5Security Advisory

TL;DR 📌

  • SAP NetWeaver Enterprise Portal contains an improper neutralization of special elements in data query logic vulnerability that allows an unauthenticated attacker to disclose or modify server information via injected JNDI environment properties or a URL used during JNDI lookup operations.
  • Highest CVSS: 6.5 (Medium).
  • Listed in CISA KEV (2026-11-20) — this is being exploited in the wild.
  • Check the advisory for fixed releases — remediation detail is in the vendor link below.
  • CVEs: CVE-2025-42884.

What it is

CVE-2025-42884 affects SAP NetWeaver Enterprise Portal. The flaw sits in data query logic that fails to properly neutralise special elements supplied in a request, allowing an attacker to inject JNDI environment properties or supply a URL used during a JNDI lookup operation.

Because the injected values are used in JNDI lookups, an attacker can cause the server to connect to a JNDI provider other than the one intended. This can lead to disclosure or modification of information about the server. SAP’s own description notes there is no impact on availability.

The attack requires no authentication and no user interaction. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms this is reachable over the network with low attack complexity and no privileges needed — exposure depends on whether the Enterprise Portal component is reachable, but no credentials are required to exploit it once reached.

The vulnerability is listed in CISA’s Known Exploited Vulnerabilities catalogue, added 2026-11-20, so it is known to be exploited.

What to do

  • Check whether SAP NetWeaver Enterprise Portal is running in your environment and confirm its exposure — this is an unauthenticated, network-reachable issue, so internet- or extranet-facing instances are the most urgent to address.
  • Consult the SAP advisory for CVE-2025-42884 directly for the fixed release and patch level; no fixed version is listed in the data available here, so do not assume a specific build is safe without checking SAP’s own notes.
  • Given its presence in the CISA KEV catalogue, treat remediation as time-sensitive rather than routine patch-cycle work, particularly for federal or regulated environments with KEV remediation deadlines.
  • Review network access controls in front of the Enterprise Portal — restricting access to trusted networks reduces exposure to this unauthenticated vector while patching is scheduled.
  • Where JNDI lookups are logged or monitored elsewhere in your SAP estate, check for unexpected JNDI provider URLs or environment property injections as part of your detection baseline.

For leadership 🧭

Executive summary. SAP NetWeaver Enterprise Portal has a flaw that lets anyone on the network redirect its JNDI lookups to a server of their choosing, exposing or altering server information without logging in. It is listed in CISA’s Known Exploited Vulnerabilities catalogue, so remediation should be treated as urgent rather than scheduled into a normal patch cycle.

Why it matters:

  • The flaw is in SAP NetWeaver Enterprise Portal’s data query logic, where unneutralised input lets an attacker inject JNDI environment properties or a lookup URL, redirecting the server to an attacker-chosen JNDI provider.
  • No authentication or user interaction is required (CVSS vector AV:N/AC:L/PR:N/UI:N), so any attacker who can reach the Enterprise Portal over the network can attempt exploitation.
  • The outcome is disclosure or modification of server information; SAP notes there is no impact on availability, so this is not a denial-of-service risk but an information and integrity exposure.
  • It is listed in CISA’s KEV catalogue (added 2026-11-20), meaning it is known to be exploited, which raises the priority for any internet- or extranet-facing Enterprise Portal instance.

Now / Next / Later:

  • Now: Identify every SAP NetWeaver Enterprise Portal instance in your estate and check whether it is reachable from the internet or an extranet — these are the most urgent to isolate or restrict immediately.
  • Next: Apply SAP’s fix for CVE-2025-42884 via the SAP advisory during your next change window, since no fixed version or build number was available to confirm here; in the meantime tighten network access controls in front of the Enterprise Portal to limit exposure to trusted networks.
  • Later: Add JNDI lookup monitoring across your SAP estate to flag unexpected provider URLs or injected environment properties, and incorporate KEV-listed SAP vulnerabilities into a fast-track patching process rather than routine cycles.

Source