CVE-2025-42884 - SAP NetWeaver Improper Neutralization of Special Elements in Data Query Logic Vulnerability

CVE-2025-42884

SAP NetWeaver Enterprise Portal - Unauthenticated JNDI Injection in EP-PIN-APF-CAT

What is SAP NetWeaver Enterprise Portal?

SAP NetWeaver is the Java and ABAP application platform underneath most of SAP's traditional business suite. The Enterprise Portal component is its web front end: a Java-based portal that aggregates SAP and non-SAP applications behind a single sign-on, serves iViews and portal pages to employees, and acts as the entry point to ERP, HR and finance systems for a large organisation's workforce.

Enterprise Portal is a particularly attractive target for two reasons. First, it is frequently published to the internet or to a partner extranet, because its whole purpose is remote access to internal business applications. Second, it sits in front of the systems that hold payroll, financial and supplier data, and it holds the session and identity material that connects a user to them. SAP NetWeaver has consequently been a recurring entry in the KEV catalog: CVE-2025-31324 and CVE-2025-42999 in the Visual Composer component were both heavily exploited during 2025.

Overview

CVE-2025-42884 is a JNDI injection vulnerability in SAP NetWeaver Enterprise Portal. An unauthenticated remote attacker can inject JNDI environment properties, or supply the URL used during a JNDI lookup, and so direct the portal to contact a JNDI provider of the attacker's choosing. SAP states the consequence as disclosure or modification of information about the server, with no impact on availability.

SAP patched it in Security Note 3660969, released on the November 2025 Security Patch Day (2025-11-11) as one of twenty-six notes, of which four were HotNews. By SAP's own rating this was a mid-tier item on that day, priority Medium at CVSS 6.5, far below the two CVSS 10.0 HotNews notes beside it. CISA's catalog title uses the CWE-943 wording, "improper neutralization of special elements in data query logic," which is the formal classification; "JNDI injection" is the more useful description.

What changed a year later is exploitation. CISA added the CVE to the KEV catalog on 2026-11-20 with a 2026-11-23 deadline, and NVD's CISA SSVC assessment marks exploitation as active, automatable yes, technical impact partial. Note the one-year gap between patch and KEV listing: this is not a new bug, it is an old patch that some organisations did not apply. As of this writing no vendor, researcher or incident responder has published details of the exploitation, named a threat actor, or released a proof of concept, so the KEV entry is currently the only public evidence that attacks are happening.

Affected Versions

Product Vulnerable Fixed
SAP NetWeaver Enterprise Portal (EP-BASIS) 7.50 Patch level per SAP Note 3660969
SAP NetWeaver Enterprise Portal (EP-RUNTIME) 7.50 Patch level per SAP Note 3660969

Onapsis records the affected application component as EP-PIN-APF-CAT. SAP does not publish fixed support package levels outside the note, which requires a customer login; retrieve the exact target patch levels from Note 3660969 for your installation.

Technical Details

JNDI, the Java Naming and Directory Interface, is the API a Java application uses to look up a named resource such as a datasource, an LDAP directory entry or a remote object. A lookup takes a provider URL and a set of environment properties that tell the runtime which naming service to talk to and how. JNDI injection is what happens when an attacker controls any of that: the application obediently contacts a server the attacker chose and processes what it sends back. The best-known instance of this class is Log4Shell, where a JNDI lookup reachable from a log string became full remote code execution.

Here the vulnerable path accepts attacker-influenced JNDI environment properties or a lookup URL on an unauthenticated request, so the portal can be pointed at an unintended JNDI provider. The attack needs no credentials, no user interaction and low complexity, which is why the exploitability subscore is the maximum 3.9. SAP caps the impact at low confidentiality and low integrity with no availability effect, so the scored outcome is leaking or altering information about the server rather than code execution, and no public analysis explains in detail where that limit comes from. Treat that ceiling with some caution: SAP's severity reflects the behaviour SAP validated, while the JNDI injection class has a history of being escalated further by researchers, and CISA's SSVC entry already rates the technical impact as partial and the attack as automatable. Neither SAP nor Onapsis has published the vulnerable endpoint or parameter.

Discovery

The Onapsis Research Labs team found and reported the vulnerability to SAP; no individual researcher is credited. Onapsis specialises in SAP security research and supported eight of the vulnerabilities fixed across seven notes on that patch day. Thomas Fritsch published the firm's patch day write-up on 2025-11-11, the same day SAP released the note.

Exploitation Context

CISA's KEV listing on 2026-11-20 is, at present, the whole of the public exploitation record. The SSVC decision point set published alongside it (exploitation active, automatable yes, technical impact partial) means CISA has evidence of active exploitation and assesses the attack as scriptable at scale. CISA's KEV entry does not flag known ransomware use.

Beyond that, nothing has been published: no threat actor attribution, no campaign name, no victim count, no indicators of compromise, no exposure figures for internet-facing Enterprise Portal instances, and no public proof of concept. There is no indication that this CVE is being chained with other SAP flaws, though SAP environments are routinely attacked by actors who already hold a working exploit chain for NetWeaver, and an unauthenticated information-disclosure primitive on the portal is a natural first step in reconnaissance for one. Organisations should treat the absence of detail as a gap in public reporting rather than as evidence that the risk is small; CISA added it to KEV for a reason, and the three-day deadline reflects that.

Remediation

  1. Apply SAP Security Note 3660969 to all SAP NetWeaver Enterprise Portal 7.50 systems running EP-BASIS or EP-RUNTIME. Retrieve the exact support package or patch level from the note using your SAP customer login. The BOD 26-04 deadline is 2026-11-23.
  2. Confirm coverage across the whole landscape, not just production. Development, quality assurance and sandbox portals are frequently internet-reachable and rarely patched on the same schedule.
  3. If you cannot patch within the deadline, remove the portal from direct internet exposure, or place it behind an authenticating reverse proxy or VPN, so unauthenticated requests cannot reach it.
  4. Restrict outbound network traffic from the NetWeaver Java application servers. A JNDI injection is only useful if the server can reach the attacker's naming service, so denying outbound LDAP, LDAPS, RMI and arbitrary HTTP from those hosts blunts the attack considerably. This is a mitigation, not a fix.
  5. Review the portal's HTTP access logs and the NetWeaver Java default trace for requests carrying JNDI-looking values (ldap://, ldaps://, rmi:// or iiop:// URLs, or java.naming property names) and for outbound connection attempts from the application server to unfamiliar hosts. Cover the period back to 2025-11-11, since the flaw has been public and unpatched on affected systems for a year.
  6. If you find evidence of exploitation, treat the portal host as untrusted: review SAP user and role changes, rotate portal service credentials and any secrets held in the Java secure store, and check for follow-on access to the backend systems the portal connects to.
  7. While you are in the note, review the other November 2025 Patch Day items that apply to your landscape, in particular the CVSS 10.0 HotNews notes 3666261 (SQL Anywhere Monitor) and 3660659 (NetWeaver AS Java deserialization).

Key Details

PropertyValue
CVE ID CVE-2025-42884
Vendor / Product SAP - NetWeaver
NVD Published2025-11-11
NVD Last Modified2026-11-20
CVSS 3.1 Score6.5
CVSS 3.1 VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
SeverityMEDIUM
CWE CWE-943 find similar ↗
CISA KEV Added2026-11-20
CISA KEV Deadline2026-11-23
Known Ransomware Use No

CVSS 3.1 Breakdown

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

Required Action

CISA BOD 26-04 Deadline: 2026-11-23. Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA's BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA's "Forensics Triage Requirements" (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Timeline

DateEvent
2025-11-11SAP releases Security Note 3660969 on the November 2025 Security Patch Day; CVE record published
2025-11-11Onapsis Research Labs, which reported the flaw, publishes its patch day analysis
2026-11-20CISA SSVC assessment records exploitation status as active
2026-11-20Added to CISA Known Exploited Vulnerabilities catalog
2026-11-23CISA BOD 26-04 remediation deadline