# CVE-2021-22519: Code injection in SiteScope

> Remote attackers can execute arbitrary code on Micro Focus SiteScope installations, requiring immediate patching by system administrators.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 May 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-2m3w-xcjp-43pq

## What is CVE-2021-22519?

CVE-2021-22519 is a critical code injection vulnerability in SiteScope, published on 28 May 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Execute arbitrary code vulnerability in Micro Focus SiteScope product, affecting versions 11.40,11.41 , 2018.05(11.50), 2018.08(11.51), 2018.11(11.60), 2019.02(11.70), 2019.05(11.80), 2019.08(11.90), 2019.11(11.91), 2020.05(11.92), 2020.10(11.93). The vulnerability could allow remote attackers to execute arbitrary code on affected installations of SiteScope.

## Which versions are affected by CVE-2021-22519?

It affects 1 product.


Products: Microfocus Sitescope.

## How do I fix CVE-2021-22519?

No fix has been published for CVE-2021-22519 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-22519 being exploited?

There is no known exploitation of CVE-2021-22519 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-22519 and fix it if it is affected.

What it is: CVE-2021-22519 is a critical code injection vulnerability in SiteScope, published on 28 May 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-22519 in the wild and no public exploit code.

Affected product: SiteScope. 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-2021-22519/ (Markdown: https://insights.sbomify.com/CVE-2021-22519/index.md)
```

## Sources

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

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