CVE-2023-23852
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 · uneditedSAP Solution Manager (System Monitoring) - version 720, does not sufficiently encode user-controlled inputs, resulting in Cross-Site Scripting (XSS) vulnerability.
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 confidenceSAP Solution Manager 720 System Monitoring feature does not properly encode user-controlled inputs, allowing injection of malicious JavaScript that executes in the context of other users' browsers when they view monitored system data.
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= 720CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed SAP Solution Manager versionQuery the SAP system for the Solution Manager version using transaction SM37 or check the SAP system information via SAPMMC or the SAP NetWeaver Administrator. Alternatively, check the SAP Note or system profile parameters that display the Solution Manager release version.Affected if The installed version is exactly 720 (version 720)
-
Verify if System Monitoring is configuredAccess the SAP Solution Manager configuration (transaction SOLMAN_SETUP or the System Monitoring work center) and check whether System Monitoring scenarios or monitoring templates have been set up for any managed systems.Affected if System Monitoring is active and configured for one or more managed systems
-
Confirm user access to monitored system dataCheck user authorizations for the System Monitoring work center (transaction SOLMAN_WORKCENTER or similar) and verify which users have roles allowing them to view monitoring data, alerts, or system health information.Affected if Users with the ability to view System Monitoring data exist in the system
-
Inspect System Monitoring for unencoded input handlingWithin the System Monitoring work center, examine how user-controlled fields (such as system aliases, hostnames, or custom monitoring object names) are rendered when displayed. Look for areas where custom inputs could be injected into the monitoring views.Affected if The System Monitoring feature accepts and displays user-supplied input without visible output encoding or sanitization
You are affected if your SAP Solution Manager is exactly version 720, System Monitoring is configured, and users can view monitoring data where unencoded user inputs are displayed.
Generated from the published advisory. Verify against your own configuration.
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 dataApply SAP security notes addressing this vulnerability and implement output encoding for user inputs in the System Monitoring functionality.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-23852 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-23852 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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