dbcve.org
Netweaver Application Server JavaApplication · Sap

CVE-2026-27674

MEDIUM · 6.1 CVSS v3.1 Published 2026-04-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Due to a Code Injection vulnerability in SAP NetWeaver Application Server Java (Web Dynpro Java), an unauthenticated attacker could supply crafted input that is interpreted by the application and causes it to reference attacker-controlled content. If a victim accesses the affected functionality, that attacker-controlled content could be executed in the victim�s browser, potentially resulting in session compromise. This could allow the attacker to execute arbitrary client-side code, impacting the confidentiality and integrity of the application, with no impact to availability.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a Code Injection (specifically Cross-Site Scripting/XSS) vulnerability in SAP NetWeaver Application Server Java's Web Dynpro Java component. An unauthenticated attacker can supply crafted malicious input that gets stored or reflected by the application, causing the victim's browser to execute attacker-controlled JavaScript when accessing the affected functionality, leading to session hijacking and arbitrary client-side code execution.

MitigationApply the relevant SAP security patch for this vulnerability. Additionally, implement robust input validation and output encoding on all user-supplied data within Web Dynpro applications to prevent XSS execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Netweaver Application Server JavaApplication
Affected:= 7.50

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify SAP NetWeaver AS Java version
    Access the SAP NetWeaver Administrator (NWA) or use transaction code SM51 in SAP GUI to view the installed software component versions. Look for the 'SAP NetWeaver Application Server Java' component and note its version number.
    Affected if The installed version is exactly 7.50
  2. Confirm Web Dynpro Java is deployed
    Check if Web Dynpro Java is installed and running. In SAP NetWeaver Administrator, navigate to Systems > Components or check via SAP transaction code SE06 -> Display Installed Software Components. Look for 'Web Dynpro Java' or 'WDJ' component.
    Affected if Web Dynpro Java component is present in the SAP system
  3. Identify active Web Dynpro applications
    Review the deployed Web Dynpro applications in the system. Use SAP transaction code SE80 or access the Web Dynpro Explorer. Document all custom and standard Web Dynpro applications currently deployed.
    Affected if Any Web Dynpro applications are deployed and accessible via HTTP/HTTPS endpoints
  4. Verify unauthenticated access to Web Dynpro endpoints
    Attempt to access known Web Dynpro URLs (typically /webdynpro/ or /sap/bc/webdynpro/) without authentication. Check if external-facing portals or transaction launcher URLs are reachable without login.
    Affected if Web Dynpro endpoints are accessible without authentication over the network

The environment is affected if SAP NetWeaver Application Server Java version 7.50 is installed and Web Dynpro Java component is deployed with unauthenticated HTTP access enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant SAP security patch for this vulnerability. Additionally, implement robust input validation and output encoding on all user-supplied data within Web Dynpro applications to prevent XSS execution.

Fix this in Netweaver Application Server Java Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27674 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-27674 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data