dbcve.org
SitescopeApplication · Microfocus

CVE-2021-22519

CRITICAL · 9.8 CVSS v3.1 Published 2021-05-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
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.

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 confidence

Micro Focus SiteScope contains a remote code execution vulnerability allowing unauthenticated remote attackers to execute arbitrary code on affected installations. The critical CVSS score of 9.8 indicates the vulnerability is easily exploitable and has complete impact on confidentiality, integrity, and availability.

MitigationUpgrade SiteScope to a patched version once available from Micro Focus. In the interim, network-segment the service, restrict access to trusted IPs only, and monitor for indicators of compromise.

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
SitescopeApplication
Affected:= 11.40= 11.41= 11.50= 11.51= 11.60= 11.70= 11.80= 11.90= 11.91= 11.92= 11.93

CVSS 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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify SiteScope is installed
    Check for SiteScope installation directories: on Windows look in C:\Program Files\Micro Focus\SiteScope\, on Linux check /opt/HP/SiteScope/ or /opt/microfocus/SiteScope/. Also check for running processes named SiteScope or sightscope.exe.
    Affected if SiteScope software is found on the system
  2. Identify installed SiteScope version
    Access the SiteScope web interface and navigate to Help > About, or check version.properties in the installation directory. On Windows you can also query the Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\HP\SiteScope for the Version value.
    Affected if The installed version matches any of: 11.40, 11.41, 11.50, 11.51, 11.60, 11.70, 11.80, 11.91, 11.92, or 11.93
  3. Confirm network accessibility of SiteScope
    Check if the SiteScope HTTP/HTTPS ports (commonly 8080, 8443, or 80/443) are listening on network interfaces accessible from untrusted networks. Use netstat -an or equivalent to list open ports and verify binding addresses.
    Affected if SiteScope web interface ports are bound to 0.0.0.0 or otherwise reachable from untrusted networks
  4. Review authentication configuration
    Inspect SiteScope configuration files (typically in /config/ or /sitescope/config/ directory) for authentication settings. Check for disabled authentication or misconfigured access controls in the main configuration file.
    Affected if Authentication is disabled, weakened, or accessible without valid credentials

If SiteScope is installed and the version is 11.40, 11.41, 11.50, 11.51, 11.60, 11.70, 11.80, 11.91, 11.92, or 11.93 with its web interface network-accessible, the environment is affected by this unauthenticated RCE vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade SiteScope to a patched version once available from Micro Focus. In the interim, network-segment the service, restrict access to trusted IPs only, and monitor for indicators of compromise.

Fix this in Sitescope Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-22519 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-22519 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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