CVE-2020-26825
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 Fiori Launchpad (News tile Application), versions - 750,751,752,753,754,755, allows an unauthorized attacker to use SAP Fiori Launchpad News tile Application to send malicious code, to a different end user (victim), because News tile does not sufficiently encode user controlled inputs, resulting in Reflected Cross-Site Scripting (XSS) vulnerability. Information maintained in the victim's web browser can be read, modified, and sent to the attacker. The malicious code cannot significantly impact the victim's browser and the victim can easily close the browser tab to terminate it.
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 confidenceSAP Fiori Launchpad News tile application versions 750-755 contains a reflected XSS vulnerability where user-controlled inputs are not properly encoded, allowing attackers to inject malicious JavaScript that executes in victims' browsers to steal session data or perform actions on behalf of users.
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= 750= 751= 752= 753= 754= 755CVSS 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.
-
Confirm SAP Fiori Launchpad News tile application is deployedAccess SAP Fiori Administration Cockpit or check SAP system documentation for installed Fiori applications. Look for the News tile application in the catalog of deployed tiles.Affected if The News tile application is present in the Fiori Launchpad configuration.
-
Identify the installed version of the News tile applicationIn SAP Fiori Administration Cockpit, navigate to the News tile application details. The version is typically displayed in the application configuration or can be retrieved via SAP transaction SE11 or SM37 checking the related component version.Affected if The installed version is exactly 750, 751, 752, 753, 754, or 755.
-
Verify the News tile is exposed to end usersCheck the SAP Fiori Launchpad group and catalog assignments. Confirm the News tile is assigned to a catalog accessible to one or more end users via the SAP Fiori My Home or launchpad configuration.Affected if The News tile is assigned to a user-accessible catalog and appears on user launchpads.
-
Determine if custom news feeds are configuredIn SAP Fiori Launchpad settings for the News tile, examine the configured news feed source. Check whether custom RSS/Atom feeds or internal news sources are assigned that accept external or user-controlled input.Affected if Custom news feeds or external URLs are configured as the news source for the tile.
A user is affected if the SAP Fiori Launchpad News tile application version is 750-755, the tile is exposed to end users, and custom or external news feeds can supply untrusted input to the tile.
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 the relevant SAP security patch for CVE-2020-26825 and ensure all user inputs in the News tile application are properly validated and output-encoded.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-26825 — 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-2020-26825 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