CVE-2019-0395
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 BusinessObjects Business Intelligence Platform (Fiori BI Launchpad), before version 4.2, allows execution of JavaScript in a text module in Fiori BI Launchpad, leading to Stored Cross Site Scripting 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 confidenceA stored cross-site scripting (XSS) vulnerability exists in SAP BusinessObjects BI Platform's Fiori BI Launchpad text module. Versions prior to 4.2 fail to properly sanitize user-supplied input in text modules, allowing authenticated attackers to inject and execute arbitrary JavaScript code in the context of other users' sessions.
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< 4.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed SAP BusinessObjects BI Platform versionAccess the SAP BusinessObjects Central Management Console (CMC) or check the version through the SAP BusinessObjects Lifecycle Manager. Typically, the version is displayed in the CMC 'About' section or can be retrieved via the SAP BusinessObjects Enterprise CA - License Keys node.Affected if The installed version is a release prior to 4.2 (for example, 4.1 SPxx, 4.0 SPxx, or earlier releases).
-
Confirm Fiori BI Launchpad is deployedCheck if the Fiori BI Launchpad web application is installed and accessible. This is typically found at paths like /BOE/BILaunchpad or /fiori/launchpad depending on configuration. Verify the web application is running on the SAP BusinessObjects web tier.Affected if Fior i BI Launchpad is deployed and accessible to users.
-
Check if text modules feature is enabledIn the Fiori BI Launchpad, navigate to the module configuration or templates. Text modules are typically available as a content type that users can create and embed within dashboards or reports. Verify if authenticated users have permission to create or edit text modules.Affected if Authenticated users can access and create text modules within Fiori BI Launchpad.
-
Verify user input handling in text modulesAs an authenticated user, create or edit a text module in Fiori BI Launchpad and attempt to insert HTML or JavaScript code (for example, <script>alert('test')</script> or an img onerror attribute) into the text content field. Save and view the module to see if the code executes or is rendered unsanitized.Affected if User-supplied HTML or JavaScript content in text modules is rendered without sanitization or encoding, executing in other users' sessions.
If the installed SAP BusinessObjects BI Platform version is below 4.2 AND the Fiori BI Launchpad with text modules is accessible to authenticated users, the environment is affected by this stored XSS vulnerability.
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 data4.2
Upgrade SAP BusinessObjects BI Platform to version 4.2 or later. Additionally, implement input validation and output encoding for all user-supplied content in the Fiori BI Launchpad, and configure Content Security Policy headers to mitigate XSS risks.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0395 — 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-2019-0395 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