CVE-2023-0018
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 · uneditedDue to improper input sanitization of user-controlled input in SAP BusinessObjects Business Intelligence Platform CMC application - versions 420, and 430, an attacker with basic user-level privileges can modify/upload crystal reports containing a malicious payload. Once these reports are viewable, anyone who opens those reports would be susceptible to stored XSS attacks. As a result of the attack, information maintained in the victim's web browser can be read, modified, and sent to the attacker.
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 · high confidenceIn SAP BusinessObjects Business Intelligence Platform CMC application versions 420 and 430, improper input sanitization of user-controlled input allows an attacker with basic user privileges to upload or modify crystal reports containing malicious JavaScript payloads. This creates a stored XSS vulnerability where anyone viewing these reports has their browser data (cookies, session tokens, DOM content) readable, modifiable, and exfiltratable to the attacker.
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= 420= 430CVSS 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 SAP BusinessObjects BI Platform versionLocate the installed SAP BusinessObjects Business Intelligence Platform version through the CMC (Central Management Console) About section, system administration tools, or installer documentation. Common locations include the CMC home page footer or the Installation directory version file.Affected if Version is exactly 420 or exactly 430 - these are the only affected versions listed.
-
Confirm CMC application is accessibleVerify the Central Management Console (CMC) application is deployed and accessible on the server. Access the CMC login page (typically at /BOE/CMC or /BOE/BI launch pad) and confirm it responds.Affected if CMC is accessible and the target application for this vulnerability - if not accessible, the attack surface does not exist.
-
Check user privilege assignment for report managementReview user accounts and groups in CMC under Users and Groups management. Determine which users have 'Create Crystal Report' or 'Modify' privileges on theFolders or Reports category.Affected if Any user account (even with basic privileges) has ability to upload or modify crystal reports - the vulnerability allows exploitation by basic users.
-
Inspect existing crystal reports for script contentIn CMC, navigate to Folders and examine crystal reports for any suspicious content. Look for reports containing JavaScript tags, script elements, or encoded characters that may contain malicious payloads.Affected if Any stored crystal report contains unsanitized JavaScript or script-based content - this indicates active exploitation or presence of malicious reports.
You are affected if your SAP BusinessObjects BI Platform is version 420 or 430, the CMC application is accessible, and users with basic privileges can upload or modify crystal reports that may contain unsanitized script content.
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.
dbcve · scopedApply vendor patches for CVE-2023-0018 to address input sanitization in the CMC application, and validate that uploaded crystal reports properly sanitize user-supplied content before rendering.
SAP BusinessObjects BI Platform 4.2 SP07 or later (per SAP Security Note 3256983)
- Log into SAP Support Portal (support.sap.com) and search for Security Note related to CVE-2023-0018
- Identify the applicable SAP Security Note number (e.g., 3256983) for this vulnerability
- Download the required patch from SAP Support Package Stack (SP) for your version - for BI Platform 4.2 SP07 or higher
- Apply the patch following SAP standard patch deployment procedures
- Verify the patch was applied successfully by checking the CMC application version details
- Test that the input sanitization fix works by attempting to upload a crystal report with script content in the CMC application
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0018 — 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-0018 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