PowerstoreosOperating system · Dell

CVE-2022-26866

MEDIUM · 5.5 CVSS v3.1 Published 2022-06-02
Fix available
A fix is available. Upgrade to 2.1.1.0 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable 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
Dell PowerStore Versions before v2.1.1.0. contains a Stored Cross-Site Scripting vulnerability. A high privileged network attacker could potentially exploit this vulnerability, leading to the storage of malicious HTML or JavaScript codes in a trusted application data store. When a victim user accesses the data store through their browsers, the malicious code gets executed by the web browser in the context of the vulnerable web application. Exploitation may lead to information disclosure, session theft, or client-side request forgery.

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

Dell PowerStore versions before v2.1.1.0 contain a stored Cross-Site Scripting (XSS) vulnerability. A high-privileged network attacker can inject malicious HTML or JavaScript code into the application's trusted data store. When victim users access this compromised data through their web browsers, the embedded scripts execute within the context of the vulnerable web application, potentially leading to information disclosure, session theft, or client-side request forgery.

MitigationUpgrade Dell PowerStore to version v2.1.1.0 or later to remediate this stored XSS vulnerability.

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
PowerstoreosOperating system
Affected:< 2.1.1.0

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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. Determine PowerStoreOS version
    Access the PowerStore management interface or CLI and retrieve the current PowerStoreOS version number. This is typically found in the system settings, About section, or by running the appropriate version command.
    Affected if The installed PowerStoreOS version is below 2.1.1.0
  2. Verify web application is accessible
    Confirm that the PowerStore web management interface is network-accessible. Check if the HTTPS portal is exposed and reachable by users.
    Affected if The web interface is accessible and the version is below 2.1.1.0
  3. Confirm high-privileged attacker access
    Review access controls and audit logs to determine if a network attacker could have obtained high-privileged credentials to inject malicious scripts into the application's data store.
    Affected if High-privileged attacker access is possible and the version is below 2.1.1.0

A user is affected if their PowerStoreOS version is below 2.1.1.0 and the web interface is accessible to trigger the stored XSS when users view compromised data.

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 2.1.1.0 or later
Fixed in 2.1.1.0
Interim mitigation

Upgrade Dell PowerStore to version v2.1.1.0 or later to remediate this stored XSS vulnerability.

Recommended fix High confidence

v2.1.1.0

  1. Upgrade PowerStore to version 2.1.1.0 or later to resolve the stored Cross-Site Scripting vulnerability
  2. Follow Dell standard upgrade procedures for PowerStore appliances
  3. After upgrade, verify the system is running version 2.1.1.0 or later
  4. Confirm the XSS vulnerability is remediated by ensuring malicious scripts are no longer executable through the affected application data store

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

Fix this in Powerstoreos Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-26866 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-26866 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