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

CVE-2026-44759

MEDIUM · 6.1 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 →
68/100
Remediation priority · Elevated
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 Enterprise Portal allows an unauthenticated attacker to inject malicious scripts into a URL parameter. The scripts are reflected in the server response and executed in a user's browser when the crafted URL is visited, leading to theft of session information, manipulation of portal content, or user redirection, resulting in a low impact on the application's confidentiality and integrity, with no impact on 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 · high confidence

This is a reflected Cross-Site Scripting (XSS) vulnerability in SAP NetWeaver Enterprise Portal where an unauthenticated attacker can inject malicious JavaScript into a URL parameter. The injected script is reflected back in the server response and executes in the victim's browser when they visit the crafted URL, enabling session theft, content manipulation, or redirection.

MitigationImplement proper input validation and output encoding for all user-supplied parameters. Apply context-aware escaping before reflecting any user input in HTML responses, and consider deploying a WAF rule as a temporary compensating control until the underlying fix is applied.

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
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 Enterprise Portal installation
    Locate the SAP NetWeaver installation directory or check system inventory for 'SAP NetWeaver Enterprise Portal' components. Look for SAP-related services running on typical ports (50000, 8000, 8080) or consult SAP LMDB (Landscape Management Database).
    Affected if SAP NetWeaver Enterprise Portal is not present on the system, the vulnerability does not apply.
  2. Determine the installed NetWeaver version
    Check the SAP system version via transaction code 'SM51' if access is available, or inspect version files in the SAP installation directory (e.g., 'sapinfo.txt' or 'kernel version' files). Compare against any available SAP security notes or patch documentation.
    Affected if The installed version cannot be determined or falls within an affected version range if such a range becomes known.
  3. Identify accessible web endpoints and parameters
    Review SAP Enterprise Portal web traffic using proxy tools or examine the SAP ICM (Internet Communication Manager) configuration for exposed URLs. Focus on endpoints that accept user-supplied query parameters.
    Affected if No web-facing parameters are found, the attack surface for reflected XSS may be limited.
  4. Test for reflected XSS in URL parameters
    Using a safe, authorized test parameter (such as a known search or navigation parameter), inject a benign test string like '<test>' into the URL and observe whether this string is reflected unchanged in the HTML response without proper encoding.
    Affected if User-supplied input is reflected directly in server responses without encoding, indicating potential XSS vulnerability.

The system is affected if it runs SAP NetWeaver Enterprise Portal and user-supplied URL parameters are reflected in responses without sanitization, allowing script injection.

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 for all user-supplied parameters. Apply context-aware escaping before reflecting any user input in HTML responses, and consider deploying a WAF rule as a temporary compensating control until the underlying fix is applied.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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