CVE-2025-26483
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, versions 4.6.2 and prior, contains an Open Redirect Vulnerability. An unauthenticated attacker could potentially exploit this vulnerability, leading to a targeted application user being redirected to arbitrary web URLs. The vulnerability could be leveraged by attackers to conduct phishing attacks that cause users to divulge sensitive information.
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 confidenceDell PowerFlex Manager versions 4.6.2 and prior contain an open redirect vulnerability. An unauthenticated attacker can craft malicious URLs containing arbitrary redirect targets that trick users into visiting attacker-controlled websites, enabling phishing attacks to harvest credentials or other sensitive information.
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< 48.383.00<= 4.6.2< 3.7.8.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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/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 the installed PowerFlex product and versionLocate the installed version through the product's web UI, CLI interface, or system inventory. For PowerFlex Manager, check the 'About' or 'System Information' section in the administration interface. For PowerFlex Appliance, check the installed catalog version via the management console or running 'systemctl status' or 'version' commands if available.Affected if The installed version matches Dell Powerflex Manager <= 4.6.2, or Dell Powerflex Appliance Intelligent Catalog < 48.383.00, or Dell Powerflex Rack < 3.7.8.0
-
Inspect web application redirect handlingReview the application configuration files and web server settings (such as nginx.conf, httpd.conf, or the application's XML/YAML configuration files) for any redirect or forwarding logic. Look for parameters that accept user-controlled input like 'redirect', 'url', 'next', 'target', or 'dest' used in redirect operations.Affected if The application contains redirect logic that accepts URL parameters without validating that the destination is a relative path or trusted domain
-
Test for open redirect vulnerabilityIf you have a test environment, send HTTP requests with external URLs in redirect-related parameters. For example, modify a suspected redirect parameter to point to an external domain (e.g., '?redirect=https://attacker.com'). Observe whether the application responds with a redirect to the untrusted domain.Affected if The application redirects to arbitrary external URLs when untrusted values are provided in redirect parameters
-
Check application security logs for suspicious redirect activityReview access logs and security event logs for patterns indicating redirect parameter manipulation, such as requests containing external domains in redirect-related parameters or unusual referrer headers.Affected if Logs show redirect parameter values pointing to untrusted or unknown external domains
You are affected if your installed Dell PowerFlex product version falls within the affected ranges AND the application exposes redirect functionality that does not validate redirect destinations to relative paths or trusted domains.
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 · scoped3.7.8.048.383.00
Apply the vendor-supplied patch/upgrade to a version newer than 4.6.2. As an interim control, implement URL validation or referrer-policy enforcement at the web application firewall or reverse proxy level to block suspicious redirect patterns.
Minimum fixed versions: Powerflex Appliance Intelligent Catalog >= 48.383.00, Powerflex Rack >= 3.7.8.0, Powerflex Manager > 4.6.2
- Identify the specific PowerFlex product in your environment (Powerflex Appliance Intelligent Catalog, Powerflex Manager, or Powerflex Rack)
- For Powerflex Appliance Intelligent Catalog: Upgrade to version 48.383.00 or later
- For Powerflex Manager: Upgrade to a version greater than 4.6.2 (contact Dell support for the latest stable release)
- For Powerflex Rack: Upgrade to version 3.7.8.0 or later
- After upgrade, verify the Open Redirect vulnerability is remediated by testing that URL redirection parameters properly reject arbitrary external URLs
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-2025-26483 — 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-26483 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