CVE-2020-26815
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 send a crafted request to a vulnerable web application. It is usually used to target internal systems behind firewalls that are normally inaccessible to an attacker from the external network to retrieve sensitive / confidential resources which are otherwise restricted for internal usage only, resulting in a Server-Side Request Forgery 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 confidenceThis is a Server-Side Request Forgery (SSRF) vulnerability in the SAP Fiori Launchpad News tile Application affecting versions 750-755. An unauthenticated attacker can send crafted requests to bypass network boundaries and access internal systems behind firewalls that would normally be inaccessible from external networks, allowing retrieval of sensitive confidential resources.
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
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/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 Fiori Launchpad versionAccess SAP Fiori Launchpad administration or check system version information. Common methods include: accessing the SAP Fiori front-end server configuration, checking the SAP_UI component version via transaction SM37 or looking at the SAP Fiori launcher URL which may display version info, or using transaction SE11 to check SAP table version data.Affected if The installed version number falls within the range 750 through 755 inclusive.
-
Verify if the News tile application is deployedAccess SAP Fiori Launchpad designer or catalog configuration. Check the available tiles in the launchpad by accessing the Fiori Launchpad URL with /sap/bc/ui5_ui5/sap/arsrvc_upb_admn/main.html or checking the SAP Fiori app catalog for the presence of News-related tile applications.Affected if The News tile application is present and deployed in the Fiori Launchpad catalog.
-
Determine if the News tile is accessible to unauthenticated usersCheck SAP Fiori Launchpad role configuration and tile catalog assignments. Verify whether anonymous access is permitted for the launchpad or specific catalog containing the News tile by reviewing the PFCG roles and the ICF (Internet Communication Framework) service configuration for the News tile endpoint.Affected if The News tile can be accessed without authentication or is assigned to a role accessible to unauthenticated users.
-
Inspect News tile URL configurationReview the News tile settings in the Fiori Launchpad designer or via backend configuration. Check if the tile is configured to fetch news from external URLs and examine what URL sources are configured, if any.Affected if The News tile is configured to fetch content from URLs and no URL allowlist is implemented.
A system is affected if SAP Fiori Launchpad with News tile application versions 750-755 is deployed and the News tile is accessible, allowing an unauthenticated attacker to make arbitrary requests to internal resources.
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 this vulnerability and implement strict input validation with URL allowlists for the News tile functionality to prevent requests to internal resources.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-26815 — 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-26815 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