CVE-2023-42478
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 Business Objects Business Intelligence Platform is vulnerable to stored XSS allowing an attacker to upload agnostic documents in the system which when opened by any other user could lead to high impact on integrity of the application.
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 Business Objects Business Intelligence Platform contains a stored cross-site scripting (XSS) vulnerability that allows authenticated users to upload malicious documents containing script payloads. When other users open these documents, the embedded JavaScript executes in their browser context, enabling attackers to hijack sessions, steal credentials, or perform actions on behalf of victims.
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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:H/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 Business Objects BI Platform versionCheck the installed version through SAP Central Management Console (CMC) under 'Servers' or by running 'cmrep -version' command, or inspect the 'boe.war' file version in the deployment directoryAffected if Installed version equals 420 or 430 (or variants such as 4.20.x or 4.30.x)
-
Verify document upload feature is accessibleLog into SAP Business Objects as a standard user and attempt to access the Documents or Web Intelligence document creation/upload functionality in the CMC or BI launch padAffected if Document upload feature is available to authenticated users without additional restrictions
-
Confirm user upload permissions existIn CMC, navigate to Users/Groups and check if standard business users have 'Create' or 'Upload' rights on the Documents folder or relevant BI repository locationsAffected if Non-admin users have document creation or upload permissions enabled
-
Inspect existing uploaded documents for script payloadsUse CMC to browse uploaded documents in the repository, or query the CMS database (CI_SYSTEMOBJECTS table) for documents with embedded JavaScript or HTML tags in their metadata or content fieldsAffected if Any documents contain unsanitized script tags, event handlers, or javascript: URIs in document titles, descriptions, or embedded content
-
Review security audit logs for XSS patternsCheck SAP Business Objects audit logs or the Central Management Server (CMS) audit database for recent document uploads containing common XSS patterns like '<script', 'javascript:', 'onerror=', 'onload=' in document metadataAffected if Audit logs show recent document uploads with XSS payload patterns in file names, titles, or content
User is affected if running version 420 or 430 with document upload functionality enabled, and either malicious documents exist in the repository or recent uploads contain XSS patterns.
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 dataImplement strict input validation and sanitization for all document uploads, apply context-aware output encoding when documents are rendered, and deploy Content Security Policy (CSP) headers to mitigate script execution. Apply vendor patches when available.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-42478 — 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-42478 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