CVE-2021-27887
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 · uneditedCross-site Scripting (XSS) vulnerability in the main dashboard of Ellipse APM versions allows an authenticated user or integrated application to inject malicious data into the application that can then be executed in a victim’s browser. This issue affects: Hitachi ABB Power Grids Ellipse APM 5.3 version 5.3.0.1 and prior versions; 5.2 version 5.2.0.3 and prior versions; 5.1 version 5.1.0.6 and prior versions.
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 confidenceA stored cross-site scripting (XSS) vulnerability exists in the main dashboard of Hitachi ABB Power Grids Ellipse APM. An authenticated user or integrated application can inject malicious JavaScript into application data that executes in the browser of other users viewing the affected dashboard.
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.1.0.0, <= 5.1.0.6>= 5.2.0.0, <= 5.2.0.3>= 5.3.0.0, <= 5.3.0.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.
-
Identify Ellipse APM versionAccess the Ellipse APM administration interface or check the product 'About' section in the application menu to find the installed version numberAffected if The installed version falls within 5.1.0.0-5.1.0.6, 5.2.0.0-5.2.0.3, or 5.3.0.0-5.3.0.1
-
Verify dashboard accessLog in to the Ellipse APM web interface and navigate to the main dashboard view used for monitoring assetsAffected if You can access the main dashboard and the application is running with authenticated user sessions
-
Inspect stored application dataExamine any user-configurable dashboard widgets, data fields, or integrated application data inputs that accept custom values for display in the dashboard (such as asset names, descriptions, or custom fields)Affected if The dashboard displays data that can be authored or modified by users or integrated applications without proper output encoding
-
Check browser for XSS executionUse browser developer tools to inspect the page source of rendered dashboard elements for unencoded HTML/JavaScript characters in displayed data fieldsAffected if Rendered dashboard content contains unescaped script tags, event handlers, or JavaScript protocol handlers in user-supplied data
You are affected if the installed Ellipse APM version is 5.1.0.0-5.1.0.6, 5.2.0.0-5.2.0.3, or 5.3.0.0-5.3.0.1 and the main dashboard is accessible to authenticated users.
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.
From vendor dataApply vendor-provided patches for the specific affected versions (5.3.0.2, 5.2.0.4, 5.1.0.7) or upgrade to a later supported version. Implement output encoding and input validation as defense-in-depth measures.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2021-27887 — 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-27887 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