# CVE-2020-6207: SAP Solution Manager Missing Authentication for Critical Function

> Unauthenticated attackers can compromise all SMDAgents connected to SAP Solution Manager due to missing authentication checks.

- **Severity:** Critical 10.0 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Mar 2020
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-r9hh-cq9h-xf68

## What is CVE-2020-6207?

CVE-2020-6207 is a critical missing authorization vulnerability in SAP Solution Manager (User Experience Monitoring), published on 10 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SAP Solution Manager (User Experience Monitoring), version- 7.2, due to Missing Authentication Check does not perform any authentication for a service resulting in complete compromise of all SMDAgents connected to the Solution Manager.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2020-6207?

It affects 1 product.


Products: Sap Solution Manager.

## How do I fix CVE-2020-6207?

No fix has been published for CVE-2020-6207 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.

## Is CVE-2020-6207 being exploited?

Yes. Attackers have exploited CVE-2020-6207 in the wild since at least 3 Nov 2021.

Public exploit code:

- PoC for CVE-2020-6207  (Missing Authentication Check in SAP Solution Manager) (github_poc): https://github.com/chipik/SAP_EEM_CVE-2020-6207
- SAP Solution Manager remote unauthorized OS commands execution (metasploit)
- SAP Solution Manager remote unauthorized OS commands execution (metasploit)
- SAP Solution Manager 7.2 - Remote Command Execution (nuclei): http/cves/2020/CVE-2020-6207.yaml

## Other vulnerabilities in SAP Solution Manager (User Experience Monitoring)

- [CVE-2020-26821](https://insights.sbomify.com/CVE-2020-26821/): Missing authorization in SAP Solution Manager (JAVA stack) (critical 10.0)
- [CVE-2020-26822](https://insights.sbomify.com/CVE-2020-26822/): Missing authorization in SAP Solution Manager (JAVA stack) (critical 10.0)
- [CVE-2020-26823](https://insights.sbomify.com/CVE-2020-26823/): Missing authorization in SAP Solution Manager (JAVA stack) (critical 10.0)
- [CVE-2020-26824](https://insights.sbomify.com/CVE-2020-26824/): Missing authorization in SAP Solution Manager (JAVA stack) (critical 10.0)
- [CVE-2020-6198](https://insights.sbomify.com/CVE-2020-6198/): Auth bypass in SAP Solution Manager (Diagnostics Agent) (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-6207 and fix it if it is affected.

What it is: CVE-2020-6207 is a critical missing authorization vulnerability in SAP Solution Manager (User Experience Monitoring), published on 10 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2020-6207 in the wild since at least 3 Nov 2021.

Affected product: SAP Solution Manager (User Experience Monitoring). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-6207/ (Markdown: https://insights.sbomify.com/CVE-2020-6207/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-6207
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-6207
- OSV: https://osv.dev/vulnerability/CVE-2020-6207

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-6207/
Summaries are generated and may contain mistakes; the official description above is the record.