CVE-2022-26867
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 · uneditedPowerStore SW v2.1.1.0 supports the option to export data to either a CSV or an XLSX file. The data is taken as is, without any validation or sanitization. It allows a malicious, authenticated user to inject payloads that might get interpreted as formulas by the corresponding spreadsheet application that is being used to open the CSV/XLSX file.
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 confidencePowerStore SW v2.1.1.0 contains a formula injection vulnerability in its data export function. Authenticated users can inject spreadsheet formulas (e.g., =, +, - prefixes) into data fields that are exported to CSV/XLSX files without sanitization, potentially leading to code execution when the file is opened in Excel or another spreadsheet application.
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< 2.1.1.0CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify PowerStore model and OS versionAccess the PowerStore management interface or run the command 'Get-PowerStoreSystem' via PowerStore API to retrieve the system model and installed PowerStoreOS versionAffected if The system is a Dell PowerStore array running PowerStoreOS version earlier than 2.1.1.0
-
Confirm data export functionality existsLocate the data export function in the PowerStore UI or API - typically found in the reporting, analytics, or export sections where users can export data to CSV/XLSX formatsAffected if The data export feature to CSV/XLSX is present and accessible to authenticated users in the environment
-
Verify user-supplied data can be included in exportsReview export configurations or test the export function with sample data to confirm that user-created entries, custom fields, or imported data can be included in the exported spreadsheet filesAffected if User-supplied or user-generated data fields are included in the exported files without sanitization of formula characters
-
Test for formula injection possibilityCreate a test record with a formula-initiating character prefix (=, +, -, @) in a data field, then export that record to CSV/XLSX and open the file in a spreadsheet application to observe if the formula is interpretedAffected if The exported file contains raw formula characters that are interpreted when opened, indicating the vulnerability is present
You are affected if you run Dell PowerStore with PowerStoreOS version below 2.1.1.0 and use the data export feature with user-supplied data that is not sanitized before export to CSV/XLSX files.
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 · scoped2.1.1.0
Implement input validation and output encoding for data exported to CSV/XLSX files, specifically escaping or removing formula-initiating characters (=, +, -, @, tab, carriage return) from user-supplied data before export.
PowerStoreOS 2.1.1.0
- Upgrade PowerStoreOS to version 2.1.1.0 or later to remediate the CSV/XLSX formula injection vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26867 — 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-2022-26867 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