CVE-2022-22546
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 HTML encoding in input control summary, an authorized attacker can execute XSS vulnerability in SAP Business Objects Web Intelligence (BI Launchpad) - version 420.
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 cross-site scripting (XSS) vulnerability exists in SAP Business Objects Web Intelligence (BI Launchpad) version 420 due to improper HTML encoding in the input control summary field. An authorized attacker can inject malicious HTML/JavaScript code that will be executed in the context of other users' sessions when they view the affected input control summary.
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= 420CVSS 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.
-
Verify SAP BusinessObjects Web Intelligence versionAccess the SAP BusinessObjects BI Launchpad and check the version information, typically found in the system information or About section of the platformAffected if The installed version is exactly 420
-
Confirm BI Launchpad accessibilityAccess the SAP BusinessObjects BI Launchpad web interface and verify it is reachableAffected if The BI Launchpad interface is accessible to users
-
Identify active Input ControlsNavigate through Web Intelligence documents or reports to determine if Input Controls are configured and in use, particularly those with summary fieldsAffected if Input Controls with summary fields are configured and accessible in the environment
-
Review logs for suspicious inputExamine application and web server logs for any unusual or malicious content in input control summary field parametersAffected if Suspicious or potentially malicious entries are found in logs related to input control summary fields
The environment is affected if SAP BusinessObjects Web Intelligence version 420 is installed and the BI Launchpad with Input Controls feature is accessible to users.
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 SAP security patches for CVE-2022-22546 and implement proper HTML encoding/escaping for all user-supplied input in the input control summary component before rendering.
SAP BusinessObjects BI Platform 4.2 SP7 or later, or 4.3
- 1. Access the SAP Support Portal at https://support.sap.com/patches
- 2. Navigate to SAP BusinessObjects Business Intelligence Platform patches
- 3. Locate the security patch for CVE-2022-22546 (typically released in the February 2022 Security Patch Day)
- 4. Apply the relevant patch to your SAP BusinessObjects BI Platform 4.2 installation
- 5. Alternatively, upgrade to SAP BusinessObjects BI Platform 4.2 SP7 or later, or 4.3 which contains the fix
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2022-22546 — 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-2022-22546 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