dbcve.org
Solution ManagerApplication · Sap

CVE-2023-0025

MEDIUM · 5.4 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 →
58/100
Remediation priority · Elevated
Remotely reachable

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 Solution Manager (BSP Application) - version 720, allows an authenticated attacker to craft a malicious link, which when clicked by an unsuspecting user, can be used to read or modify some sensitive information or craft a payload which may restrict access to the desired resources.

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 web-based vulnerability in SAP Solution Manager's BSP (Business Server Pages) application version 720. An authenticated attacker can craft a malicious link containing malicious script payloads that, when clicked by an unsuspecting authenticated user, can be used to read or modify sensitive information or restrict access to resources. This appears to be a reflected cross-site scripting (XSS) vulnerability requiring user interaction.

MitigationApply the relevant SAP Security Note to patch the BSP application. Implement proper input validation and output encoding for user-supplied parameters in the affected BSP components.

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
Solution ManagerApplication
Affected:= 720

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Verify SAP Solution Manager version
    Check the installed SAP Solution Manager version by accessing the system information in the SAP GUI (System > Status) or via transaction SM37, or query the SAP table VERSION for component ST. Compare the version number to 720.
    Affected if The installed version is exactly 720.
  2. Confirm BSP application is accessible
    Access the SAP Solution Manager BSP application via HTTP/HTTPS. Typically found at paths like /sap/bc/bsp or /sap/bc/ui5_ui5. Verify the BSP application is running and reachable.
    Affected if The BSP application is exposed and reachable over the network.
  3. Check if SAP Solution Manager is accessible without authentication
    Attempt to access the SAP Solution Manager login page or BSP endpoints without providing credentials. Note whether authentication is enforced.
    Affected if The BSP application can be accessed and does not properly sanitize reflected parameters.
  4. Inspect browser interaction with BSP URLs
    Log into SAP Solution Manager and navigate to known BSP pages. Examine URL parameters in the browser address bar for unsanitized input reflected back into the page. Look for parameters that might reflect user-supplied values without encoding.
    Affected if URL parameters are reflected in the response without proper encoding.
  5. Review web server logs for XSS indicators
    Examine SAP ICM (Internet Communication Manager) logs and web dispatcher logs for unusual patterns in URL parameters that may indicate XSS probes or exploitation attempts. Look for script tags or HTML elements in request parameters.
    Affected if Log entries show suspicious script payloads in BSP-related requests.

A user is affected if they are running SAP Solution Manager version 720 with the BSP application accessible and user-supplied parameters are reflected without encoding in the application responses.

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 Note to patch the BSP application. Implement proper input validation and output encoding for user-supplied parameters in the affected BSP components.

Fix this in Solution Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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