CVE-2026-35069
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 · uneditedDell PowerFlex Manager, version(s) prior to 5.1.0.1, contain(s) an Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability. A low privileged attacker with adjacent network access could potentially exploit this vulnerability, leading to Script injection.
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 confidenceDell PowerFlex Manager versions prior to 5.1.0.1 contain a SQL injection vulnerability where improper neutralization of special elements in SQL commands allows a low-privileged attacker with adjacent network access to inject malicious SQL queries, potentially leading to script injection.
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< 4.5.5.2>= 4.6.0, < 5.1.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
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/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 PowerFlex Manager installed versionAccess the Dell PowerFlex Manager web interface or use the system's version reporting tool (typically found in Admin > System > About or via CLI: 'flexi version' or similar command). Check the build/version number displayed.Affected if The displayed version falls outside the fixed range - specifically if it is below 4.5.5.2, or between 4.6.0 and 5.1.0.0 (inclusive of 4.6.x through 5.0.x). Versions 5.1.0.1 and later are NOT affected.
-
Confirm version is in vulnerable rangeDocument the exact version number found. The vulnerable ranges are: any version prior to 4.5.5.2, OR any version from 4.6.0 up to but not including 5.1.0.1.Affected if Your installed version matches either < 4.5.5.2 OR >= 4.6.0 and < 5.1.0.1.
-
Verify adjacent network accessibilityDetermine if the PowerFlex Manager interface is accessible from network segments outside the trusted management network. Check firewall rules, VLAN configurations, and access control lists governing the management interface (typically ports 443, 4444, or custom management ports).Affected if The management interface is exposed to adjacent (non-local) network segments, allowing an attacker with adjacent network access to reach the SQL injection entry point.
-
Check for low-privileged user existenceReview user accounts in PowerFlex Manager. Identify if any accounts with low-privileged roles (read-only, operator, or standard user roles) exist in the system.Affected if Low-privileged user accounts exist in the system, as the CVE specifically notes exploitation requires a low-privileged attacker.
You are affected if your Dell PowerFlex Manager version is below 4.5.5.2, or between 4.6.0 and 5.0.x, AND the management interface is network-accessible to low-privileged 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.
dbcve · scoped4.5.5.25.1.0.1
Upgrade Dell PowerFlex Manager to version 5.1.0.1 or later to obtain the vendor patch that addresses the SQL injection vulnerability.
5.1.0.1 or later
- 1. Backup the current PowerFlex Manager configuration and data
- 2. Schedule a maintenance window for the upgrade
- 3. Download Dell PowerFlex Manager version 5.1.0.1 or later from Dell support portal (www.dell.com/support)
- 4. Review Dell PowerFlex Manager upgrade documentation for your specific deployment type
- 5. Follow the standard Dell upgrade procedure to apply version 5.1.0.1 or latest available version
- 6. After upgrade, verify the PowerFlex Manager services are running correctly
- 7. Validate that the SQL injection vulnerability is no longer present by reviewing system logs
- 8. Confirm normal operations are functioning as expected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35069 — 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-2026-35069 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