dbcve.org
Netweaver Application Server AbapApplication · Sap

CVE-2023-26459

HIGH · 7.4 CVSS v3.1 Published 2023-03-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Remotely reachable Zero-click

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 improper input controls In SAP NetWeaver AS for ABAP and ABAP Platform - versions 700, 701, 702, 731, 740, 750, 751, 752, 753, 754, 755, 756, 757, 791, an attacker authenticated as a non-administrative user can craft a request which will trigger the application server to send a request to an arbitrary URL which can reveal, modify or make unavailable non-sensitive information, leading to low impact on Confidentiality, Integrity and 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

This is a Server-Side Request Forgery (SSRF) vulnerability in SAP NetWeaver AS for ABAP. Due to improper input controls, an authenticated non-administrative user can craft malicious requests that force the application server to send requests to arbitrary URLs, potentially allowing reconnaissance, data exfiltration via internal services, or denial of service.

MitigationApply the relevant SAP security patch for CVE-2023-26459 and implement proper input validation/sanitization on all user-supplied URL parameters to prevent arbitrary request redirection by the server.

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
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L

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 version
    Use transaction code SM51 or check the SAP system landscape directory (SLD) to retrieve the installed SAP NetWeaver Application Server ABAP version number
    Affected if The displayed version matches any of these: 700, 701, 702, 731, 740, 750, 751, 752, 753, 754, 755, or 756
  2. Verify exposed web interfaces
    Check if ICM (Internet Communication Manager) or Web Dynpro ABAP interfaces are accessible externally using transaction SMICM or by reviewing HTTP port configurations in the SAP system
    Affected if Web-based URLs or RFC endpoints are accessible without proper network segmentation
  3. Review authentication configuration
    Use transaction SU01 to verify user authentication settings, and check whether non-administrative users have access to transaction codes that handle URL parameters such as RFC or HTTP destinations (transaction SM59)
    Affected if Non-administrative users can access transaction SM59 or similar URL-handling transactions without restriction
  4. Inspect system logs for suspicious outbound requests
    Use transaction SM37 or ST03N to review job logs, and check transaction SLG1 for application logs looking for outbound HTTP/RFC requests from the ABAP server to unexpected or internal IP addresses
    Affected if Logs show outbound requests from the SAP server to arbitrary URLs, especially internal infrastructure, that were initiated by user-triggered transactions

A user is affected if the installed SAP NetWeaver AS ABAP version matches any of the listed affected versions AND the system exposes web interfaces or allows non-administrative users access to URL-handling transactions.

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 the relevant SAP security patch for CVE-2023-26459 and implement proper input validation/sanitization on all user-supplied URL parameters to prevent arbitrary request redirection by the server.

Recommended fix Moderate confidence

Upgrade to a version newer than 791 or apply the SAP Security Note patch for your specific version

  1. 1. Identify your current SAP NetWeaver AS for ABAP version and Support Package Stack (SPS) level
  2. 2. Access the SAP Support Portal (launchpad.support.sap.com) and search for SAP Security Note CVE-2023-26459
  3. 3. Review the applicable SAP Note for the specific patch/Support Package that addresses this SSRF vulnerability
  4. 4. Apply the recommended patch or upgrade to a version beyond the affected versions listed (700, 701, 702, 731, 740, 750, 751, 752, 753, 754, 755, 756, 757, 791)
  5. 5. After applying the patch, verify the fix by testing that the SSRF vulnerability is no longer exploitable
  6. 6. Ensure proper authentication and authorization controls remain in place for users
Caveat Review SAP Note for any configuration changes or ABAP code adjustments required after patching; test thoroughly in a non-production system first

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
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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