Netweaver Application Server For JavaApplication · Sap

CVE-2023-26460

MEDIUM · 5.3 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 →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Cache Management Service in SAP NetWeaver Application Server for Java - version 7.50, does not perform any authentication checks for functionalities that require user identity

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

The Cache Management Service in SAP NetWeaver Application Server for Java v7.50 lacks authentication checks on functions that should require user identity. This allows unauthenticated remote attackers to access cache management functionality that should be restricted to authenticated users, potentially exposing or manipulating cached data.

MitigationApply the relevant SAP security patch for CVE-2023-26460. Until patched, restrict network access to the Cache Management Service through network segmentation or firewall rules to limit exposure to untrusted networks.

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 For JavaApplication
Affected:= 7.50

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 for Java version
    Execute the SAP J2EE engine version command: using SAP Management Console or execute 'j2eeadmin -sh Version' or check via SAP MMC snap-in under 'J2EE Engine > System > Information'. Look for the version string in the output.
    Affected if The installed version is exactly 7.50 (the only affected version per this CVE).
  2. Locate the Cache Management Service port
    Check SAP J2EE cluster configuration files: review the 'cluster.xml' or 'server.xml' files in the usr/sap/<SID>/<instance>/j2ee/cluster/config directory. Search for entries containing 'Cache' or 'CacheManager' service definitions and note the associated port number.
    Affected if The Cache Management Service is defined and exposed on a network port in the configuration.
  3. Verify service network accessibility
    From a remote system or using netstat on the SAP host, check if the Cache Management Service port (typically found in step 2) is listening on an external network interface. Use command: 'netstat -an | grep <port>' or 'telnet <host> <port>' from an untrusted network segment.
    Affected if The service port is bound to 0.0.0.0 or an external IP address (not bound to 127.0.0.1 only).
  4. Confirm unauthenticated access exposure
    Attempt a curl or HTTP request to the Cache Management Service endpoint: 'http://<hostname>:<port>/cachemanager' or similar cache management URL without providing any SAP authentication credentials. Check if the application returns cache management functionality or data instead of redirecting to a login page.
    Affected if The service responds with cache management interface or data without requiring authentication.

You are affected if you run SAP NetWeaver Application Server for Java version 7.50 AND the Cache Management Service port is network-accessible AND the service responds to unauthenticated requests.

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 the relevant SAP security patch for CVE-2023-26460. Until patched, restrict network access to the Cache Management Service through network segmentation or firewall rules to limit exposure to untrusted networks.

Fix this in Netweaver Application Server For Java Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-26460 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-26460 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