CVE-2021-40096
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 · uneditedA 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 modification of the authorisationUrl in some integration configurations.
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 confidenceAn XSS vulnerability in SquaredUp for SCOM 5.2.1.6654 allows remote attackers to inject arbitrary web scripts or HTML through the authorisationUrl parameter in integration configurations.
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< 5.3.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm SquaredUp for SCOM is installedCheck for the SquaredUp web application in IIS or the server's installed programs. Look for the SquaredUp for SCOM application in the web server's site list, typically accessible on port 80/443.Affected if SquaredUp for SCOM is not installed on the server
-
Identify the installed versionLocate the version information in the SquaredUp installation directory, typically found in a version.txt file, in the application header, or via the About page in the SquaredUp web interface.Affected if The installed version is below 5.3.1 (any version from 5.2.1.6654 up to but not including 5.3.1)
-
Check for integration configurationsAccess the SquaredUp admin or configuration area and navigate to Integrations or Data sources. Look for any integration configurations that include an authorisationUrl parameter.Affected if Integration configurations with an authorisationUrl parameter exist and the version is vulnerable
The environment is affected if SquaredUp for SCOM is installed with a version lower than 5.3.1 and integration configurations containing an authorisationUrl parameter are present.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.3.1
Update to a patched version of SquaredUp for SCOM or implement input validation/sanitization on the authorisationUrl parameter to prevent script injection.
5.3.1 or later
- 1. Backup your current SquaredUp for SCOM installation and configuration
- 2. Download SquaredUp for SCOM version 5.3.1 or later from the official vendor download portal
- 3. Apply the upgrade following the standard SquaredUp upgrade procedure documented in their knowledge base
- 4. After upgrade, verify the integration configuration settings and ensure the authorisationUrl parameter is properly sanitized
- 5. Test that the integration configurations work correctly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-40096 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-40096 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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