CVE-2024-30476
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 contains a Stored Cross-Site Scripting Vulnerability in the PowerStore Manager. A remote authenticated low-privileged malicious actor could potentially exploit this vulnerability, it could lead to script execution in the client browser.
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 confidenceThis is a stored cross-site scripting (XSS) vulnerability in Dell PowerStore Manager where a low-privileged authenticated user can inject malicious JavaScript into input fields that are later rendered without proper output encoding, allowing script execution in other users' browsers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Confirm Dell PowerStore Manager installationLocate the PowerStore Manager application on the system. This is typically accessed via web interface on port 443/8443 or through the PowerStore management software installed on a management station. Check for Dell PowerStore binaries, services, or the management UI endpoint.Affected if Dell PowerStore Manager software is present and running on the system
-
Verify Manager web interface is accessibleAccess the PowerStore Manager web interface by navigating to the management URL (commonly https://<PowerStore-IP>/manager or similar). Confirm the login page loads and the application is operational.Affected if The PowerStore Manager web interface is accessible and operational
-
Identify input fields in the Manager interfaceLog into PowerStore Manager with a low-privileged user account. Navigate through common input areas such as: system configuration fields, device naming, user profile fields, alert settings, or any text input forms. Note which fields accept user-supplied text.Affected if User-accessible input fields exist in the Manager interface that accept text input
-
Check version against affected releasesIn the PowerStore Manager interface, locate the version information (typically in Settings > About, Help > System Information, or the login page footer). Compare the installed version number to any official Dell security advisories for CVE-2024-30476 to determine if it falls within the affected range.Affected if The installed PowerStore Manager version matches the affected versions listed in the Dell security advisory for this CVE
A user is affected if Dell PowerStore Manager is installed, the web interface is accessible, and the installed version falls within the vulnerable version range published by Dell for CVE-2024-30476.
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 dataImplement proper input validation and output encoding/escaping for all user-supplied data displayed in the PowerStore Manager interface. Apply context-appropriate sanitization based on where the data is rendered (HTML, JavaScript, attributes, etc.).
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-30476 — 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-2024-30476 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