CVE-2020-26830 json
SAP Solution Manager 7.2 (User Experience Monitoring), version - 7.2, does not perform necessary authorization checks for an authenticated…
published 5y ago modified 4mo ago also EUVD-2020-19366
- cvss
- 7.6
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.5%
- EPSS 1.5% chance of exploitation in 30 days, percentile 73%
- public exploits
- 0
- none known
Summary
SAP Solution Manager 7.2 (User Experience Monitoring), version - 7.2, does not perform necessary authorization checks for an authenticated user. Due to inadequate access control, a network attacker authenticated as a regular user can use operations which should be restricted to administrators. These operations can be used to Change the User Experience Monitoring configuration, obtain details about the configured SAP Solution Manager agents, Deploy a malicious User Experience Monitoring script.
Is CVE-2020-26830 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.45% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 7.6 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L |
| NVD | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N |
| NVD | 2.0 | 5.5 | AV:N/AC:L/Au:S/C:P/I:P/A:N |
Affected products
- SAP SE SAP Solution Manager (User Experience Monitoring)
Classification
- Weakness
-
- CWE-862 Missing Authorization
References
-
wiki.scn.sap.com
/wiki/pages/viewpage.action?pageId=564757079
vendor-advisory
-
launchpad.support.sap.com
/#/notes/2983204
permissions-required, vendor-advisory
-
seclists.org
/fulldisclosure/2021/Jun/29
mailing-list, third-party-advisory
-
packetstormsecurity.com
/files/163161/SAP-Solution-Manager-7.2-Missing-Authorization.html
third-party-advisory
Sources
- CVE List CVE-2020-26830
- NVD CVE-2020-26830
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.