dbcve.org
SquaredupApplication

CVE-2021-40093

MEDIUM · 5.4 CVSS v3.1 Published 2021-12-07
Fix available
A fix is available. Upgrade to 5.3.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
A cross-site scripting (XSS) vulnerability in integration configuration in SquaredUp for SCOM 5.2.1.6654 allows remote attackers to inject arbitrary web script or HTML via dashboard actions.

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 · high confidence

An XSS vulnerability exists in SquaredUp for SCOM version 5.2.1.6654 within the integration configuration feature. The vulnerability allows remote attackers to inject arbitrary JavaScript or HTML code through dashboard actions due to insufficient input validation/sanitization.

MitigationApply vendor patch or upgrade to a patched version. Implement output encoding and input validation on dashboard action parameters in the integration configuration module.

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
SquaredupApplication
Affected:< 5.3.1

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 checks

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

  1. Identify SquaredUp for SCOM installation
    Locate the SquaredUp for SCOM installation directory and check the product version file or About page within the application
    Affected if The installed version cannot be determined or is older than 5.3.1
  2. Verify installed version against affected range
    Compare your installed version number to the affected range: versions < 5.3.1. Check product documentation or the application's version display
    Affected if The installed version is 5.2.1.6654 or any version prior to 5.3.1
  3. Confirm integration configuration feature is in use
    Navigate to the integration configuration module within the SquaredUp web interface or check configuration files for active integrations
    Affected if The integration configuration feature is enabled and configured with any dashboard actions
  4. Inspect dashboard action configurations
    Review integration configuration settings, specifically examining dashboard action parameters for any custom or user-supplied values
    Affected if Dashboard actions exist in the integration configuration with unsanitized input fields
  5. Check for signs of XSS exploitation
    Review web server logs and application audit logs for suspicious patterns in dashboard action parameters, such as script tags or JavaScript event handlers
    Affected if Logs contain requests with malicious script content in integration configuration parameters

If SquaredUp for SCOM version is below 5.3.1 and the integration configuration feature with dashboard actions is in use, the environment is affected by this XSS 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.

dbcve · scoped
Upgrade available Upgrade to 5.3.1 or later
Fixed in 5.3.1
Interim mitigation

Apply vendor patch or upgrade to a patched version. Implement output encoding and input validation on dashboard action parameters in the integration configuration module.

Recommended fix Moderate confidence

5.3.1 or later

  1. Back up your current SquaredUp configuration and database
  2. Download SquaredUp version 5.3.1 or later from the official vendor portal
  3. Stop the SquaredUp web server/IIS application pool
  4. Install the upgrade following standard SquaredUp upgrade procedures
  5. Verify the upgrade was successful by logging into the web interface
  6. Test that dashboard actions function correctly and the XSS vulnerability is resolved
  7. Confirm the new version is displayed correctly in the product UI

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Squaredup Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-40093 — 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-40093 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