dbcve.org
Netweaver Application Server AbapApplication · Sap

CVE-2023-25614

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
SAP NetWeaver AS ABAP (BSP Framework) application - versions 700, 701, 702, 731, 740, 750, 751, 752, 753, 754, 755, 756, 757, allow an unauthenticated attacker to inject the code that can be executed by the application over the network. On successful exploitation it can gain access to the sensitive information which leads 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 · moderate confidence

Code injection vulnerability in SAP NetWeaver AS ABAP BSP Framework allowing unauthenticated attackers to inject malicious code that gets executed by the application, potentially exposing sensitive information with limited impact on confidentiality and integrity.

MitigationApply SAP security patches for CVE-2023-25614 or upgrade to a supported version outside the affected list; validate that BSP applications do not accept unsanitized user input that could be interpreted as executable code.

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. Identify SAP NetWeaver AS ABAP installation
    Check for SAP NetWeaver AS ABAP processes or services running on the system, or query the SAP system via transaction SM51 (Server Instances) or SAP MII version checks
    Affected if SAP NetWeaver AS ABAP is not present on the system, the vulnerability does not apply
  2. Determine ABAP version
    Execute transaction SLICENSE or check the SAP kernel version via kernel executables (sapkernel and related binaries). The version is typically displayed as a 4-digit number (e.g., 756 for SAP_BASIS 756)
    Affected if The installed version matches one of the affected versions: 700, 701, 702, 731, 740, 750, 751, 752, 753, 754, 755, or 756
  3. Check if BSP Framework is enabled
    Verify if Business Server Pages (BSP) runtime is active by checking transaction SICF (Active HTTP Service Hierarchy) for BSP-related services, or query the BSP application configuration via transaction SE80
    Affected if BSP Framework is enabled and accessible via HTTP/HTTPS endpoints, creating the attack surface for code injection

The system is affected only if SAP NetWeaver AS ABAP is running with a version matching 700, 701, 702, 731, 740, 750, 751, 752, 753, 754, 755, or 756 AND the BSP Framework is enabled and exposed to unauthenticated users.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply SAP security patches for CVE-2023-25614 or upgrade to a supported version outside the affected list; validate that BSP applications do not accept unsanitized user input that could be interpreted as executable code.

Recommended fix Moderate confidence
  1. Check SAP Security Note for CVE-2023-25614 in SAP Support Portal (support.sap.com)
  2. Apply the relevant SAP Note/patch for your specific NetWeaver AS ABAP version
  3. After applying the patch, verify the BSP Framework components are updated
  4. Test the application to confirm XSS vulnerability is remediated

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Netweaver Application Server Abap 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-25614 — 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-25614 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