dbcve.org
Netweaver As Abap Business Server PagesApplication · Sap

CVE-2023-24521

MEDIUM · 6.1 CVSS v3.1 Published 2023-02-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 insufficient input sanitization, SAP NetWeaver AS ABAP (BSP Framework) - versions 700, 701, 702, 731, 740, 750, 751, 752, 753, 754, 755, 756, 757, allows an unauthenticated user to alter the current session of the user by injecting the malicious code over the network and gain access to the unintended data. This may lead to a limited impact on the confidentiality and the integrity 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 · high confidence

Cross-site scripting (XSS) vulnerability in SAP NetWeaver AS ABAP Business Server Pages (BSP) Framework. An unauthenticated attacker can inject malicious script code through insufficient input sanitization, allowing session hijacking and unauthorized data access.

MitigationApply SAP Security Notes to address input validation in the BSP Framework. Review and sanitize all user inputs in BSP applications. Implement output encoding and CSP headers where possible.

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 As Abap Business Server PagesApplication
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. Confirm SAP NetWeaver AS ABAP is installed
    Check if the system is running SAP NetWeaver AS ABAP by reviewing system information via transaction SM51 or checking the SAP system landscape. Look for ABAP application server components.
    Affected if The system is not running SAP NetWeaver AS ABAP - this CVE only affects that specific platform.
  2. Identify the installed ABAP version
    Use transaction SM51 to view the release version, or check the SAP system version via the SAP Logon pad or system information. Compare the version number (700, 701, 702, 731, 740, 750, 751, 752, 753, 754, 755, or 756) against the affected versions list.
    Affected if The installed version matches one of the listed affected versions: 700, 701, 702, 731, 740, 750, 751, 752, 753, 754, 755, or 756.
  3. Verify BSP Framework is active
    Check if Business Server Pages (BSP) functionality is enabled by reviewing the SAP system configuration. Use transaction SICF to verify that BSP-related HTTP services are active. BSP applications are managed via transaction SE80 under the BSP application node.
    Affected if BSP Framework is enabled and accessible via HTTP/HTTPS services - the XSS vulnerability requires BSP to be running to be exploitable.
  4. Identify exposed BSP applications
    Review active BSP applications deployed on the system using transaction SE80 (look under BSP Applications) or by checking the BSP application registry. Identify which applications accept user input through HTTP parameters.
    Affected if BSP applications that handle user input are exposed without proper input validation - this is where the XSS flaw can be triggered.
  5. Review recent security logs for XSS indicators
    Examine SAP security audit logs (transaction SM37 or security-related logs) for any suspicious patterns indicating XSS attempts or unusual script injection via BSP pages. Check HTTP access logs if available.
    Affected if There are logged attempts at injecting script content through BSP parameters, which would confirm active exploitation attempts.

The environment is affected if it runs SAP NetWeaver AS ABAP versions 700-756 with the BSP Framework enabled and exposed BSP applications that handle user input without proper sanitization.

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 SAP Security Notes to address input validation in the BSP Framework. Review and sanitize all user inputs in BSP applications. Implement output encoding and CSP headers where possible.

Fix this in Netweaver As Abap Business Server Pages Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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