dbcve.org
Netweaver Application Server AbapApplication · Sap

CVE-2026-27682

MEDIUM · 6.1 CVSS v3.1 Published 2026-05-12
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 reflected cross-site scripting (XSS) vulnerability in SAP NetWeaver Application Server ABAP (Applications based on Business Server Pages), an unauthenticated attacker could craft a URL that exploits an unprotected URL parameter to embed a malicious script. If a victim clicks the link, the injected input is processed during web page generation, resulting in the execution of malicious content in the victim�s browser context. This could allow the attacker to access and/or modify information, 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

A reflected cross-site scripting (XSS) vulnerability exists in SAP NetWeaver Application Server ABAP when processing Business Server Pages (BSP). An unauthenticated attacker can embed malicious script code into a URL parameter that gets reflected back without proper sanitization during page generation, allowing execution in the victim's browser context.

MitigationImplement proper input validation and output encoding for all URL parameters in the affected BSP pages. Consider deploying a web application firewall (WAF) as an interim control.

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 AbapApplication
Affected:= 700= 701= 702= 731= 740= 750= 751= 752= 753= 754= 755= 756

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. Verify SAP NetWeaver AS ABAP version
    Check the SAP system version by running transaction SM51 or using the SAP kernel version check (sapkernel -V). Compare the displayed version against the affected list: 700, 701, 702, 731, 740, 750, 751, 752, 753, 754, 755, 756.
    Affected if The installed SAP NetWeaver AS ABAP version matches one of the listed affected versions.
  2. Confirm BSP is enabled
    Check if Business Server Pages are enabled by accessing transaction SICF, filtering for BSP services, or checking the ICM monitor (transaction SMICM) for HTTP/HTTPS services that serve BSP applications.
    Affected if BSP-related HTTP services are active and accessible on the SAP system.
  3. Identify exposed BSP applications
    Review transaction SE80 or use transaction BSP_IDOC to list deployed BSP applications. Check which BSP applications are exposed via the Internet Communication Manager (ICM) and accessible via HTTP/HTTPS.
    Affected if Any BSP application is exposed via HTTP/HTTPS without proper input validation on URL parameters.
  4. Test for reflected XSS in BSP URLs
    Identify BSP pages by accessing known BSP entry points (for example, URLs containing /sap/bc/bsp). Inject a test script payload into URL parameters and observe if the payload is reflected unencoded in the HTTP response.
    Affected if URL parameters in BSP pages reflect user input without HTML encoding, allowing script execution in the browser.

If the SAP NetWeaver AS ABAP version is in the affected list and BSP applications are accessible via HTTP/HTTPS, the system is likely vulnerable to reflected XSS in BSP.

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 URL parameters in the affected BSP pages. Consider deploying a web application firewall (WAF) as an interim control.

Fix this in Netweaver Application Server Abap Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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