CVE-2025-32748
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) a Host Header Injection vulnerability. An unauthenticated attacker with remote access could potentially exploit this vulnerability to trigger redirections.
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 Host Header Injection vulnerability. An unauthenticated remote attacker can manipulate the HTTP Host header to trigger arbitrary redirections, potentially leading to phishing attacks or manipulation of application-generated URLs.
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< 3.8.4.1>= 3.9.0.0, < 3.9.1.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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 PowerFlex Manager versionAccess the PowerFlex Manager admin interface or check system information files. Common locations include the About page in the UI, or run: /opt/dell/powerflex/bin/sdf -version or similar version command provided by Dell documentation.Affected if The installed version is < 3.8.4.1, OR >= 3.9.0.0 and < 3.9.1.1, OR < 5.1.0.1 (all prior to the fixed release)
-
Verify web interface is accessibleConfirm the PowerFlex Manager web interface is running and accessible over HTTP/HTTPS. Try accessing the login page URL.Affected if The web interface is exposed and reachable, as the vulnerability is exploited via HTTP Host header manipulation
-
Check redirect configurationExamine the application server configuration (e.g., Apache, Nginx, or embedded server logs) for redirect rules. Look for HTTP 30x responses that use the Host header value in the Location header.Affected if The application performs server-side redirects based on the Host header without validation, which is the default vulnerable behavior
-
Inspect Host header handlingSend a crafted request with a malicious Host header (e.g., Host: evil.com) and observe if the application redirects to the attacker-controlled domain. This can be tested with curl -H 'Host: evil.com' https://your-powerflex-url/Affected if The application reflects the attacker-supplied Host header in redirect Location headers, confirming the vulnerability is present
You are affected if PowerFlex Manager version is prior to 5.1.0.1 (or specifically < 3.8.4.1, or >= 3.9.0.0 and < 3.9.1.1) AND the web interface is accessible and performs redirects based on the Host header.
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 data3.8.4.13.9.1.1
Upgrade to PowerFlex Manager version 5.1.0.1 or later. As an interim measure, implement server-side validation of the Host header using a whitelist of allowed values and ensure all redirects use absolute URLs with trusted domains.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32748 — 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-2025-32748 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