dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-44752

HIGH · 8.2 CVSS v3.1 Published 2026-07-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
Remotely reachable No privileges 5 weeks old

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
SAP NetWeaver Application Server Java allows an unauthenticated attacker to inject malicious JavaScript through crafted URLs. When a victim accesses such a URL, the script executes in the user's browser, allowing the attacker to access sensitive session information and modify non-sensitive data displayed in the client�s browser. This results in a high impact on confidentiality, low impact on integrity with no impact on availability of the application.

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 reflected Cross-Site Scripting (XSS) vulnerability in SAP NetWeaver Application Server Java. An unauthenticated attacker can inject malicious JavaScript through specially crafted URLs. When victims access these URLs, the script executes in their browsers, enabling the attacker to steal sensitive session information and modify non-sensitive data displayed in the client's browser.

MitigationImplement proper input validation and output encoding on all user-supplied parameters before rendering in browsers. Apply vendor-supplied security patches for SAP NetWeaver AS Java when available.

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

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
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/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. Confirm SAP NetWeaver AS Java is running
    Identify if the target system runs SAP NetWeaver Application Server Java by checking for typical HTTP response headers (e.g., 'SAP' or 'J2EE' headers), default ports (5xx00, 5xx01), or by reviewing infrastructure documentation
    Affected if The system is confirmed to be running SAP NetWeaver Application Server Java
  2. Identify the installed NetWeaver version
    Access the SAP NetWeaver Administrator (NWA) console or check the SAP JVM version via the command 'java -version' on the server. Alternatively, query the SAP MII or BSP application version endpoints if accessible
    Affected if The installed version cannot be determined or is within an unpatched vulnerable release of SAP NetWeaver AS Java
  3. Locate web-facing endpoints accepting user input
    Review SAP transaction codes (such as SE80, SICF) or scan for publicly accessible SAP BSP applications, Web Dynpro ABAP, or SAP Gateway services that handle URL parameters
    Affected if User-supplied parameters are reflected in HTML responses without apparent sanitization
  4. Test for reflected XSS in URL parameters
    Craft test payloads such as '<script>alert(1)</script>' in URL query parameters pointing to identified SAP endpoints. Use a browser or HTTP tool to send the request and inspect if the payload appears unescaped in the response body
    Affected if The payload renders as literal HTML or executes JavaScript in the browser without encoding or validation applied
  5. Verify the attack does not require authentication
    Confirm the vulnerable endpoint is accessible without requiring login credentials by attempting the crafted URL from an unauthenticated browser session
    Affected if The crafted URL triggers script execution in a victim's browser without any prior authentication to the SAP system

A user is affected if SAP NetWeaver Application Server Java is running, a vulnerable unpatched version is in use, and publicly accessible URL parameters reflect unsanitized input that executes JavaScript when a victim clicks a crafted link.

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

Implement proper input validation and output encoding on all user-supplied parameters before rendering in browsers. Apply vendor-supplied security patches for SAP NetWeaver AS Java when available.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44752 — 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-44752 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