CVE-2025-26514
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 · uneditedStorageGRID (formerly StorageGRID Webscale) versions prior to 11.8.0.15 and 11.9.0.8 are susceptible to a Reflected Cross-Site Scripting vulnerability. Successful exploit could allow an attacker to view or modify configuration settings or add or modify user accounts but requires the attacker to know specific information about the target instance and then trick a privileged user into clicking a specially crafted link.
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 confidenceReflected Cross-Site Scripting (XSS) vulnerability in StorageGRID Webscale versions prior to 11.8.0.15 and 11.9.0.8 allows attackers to inject malicious scripts through specially crafted links. Successful exploitation requires the attacker to know specific target instance information and trick a privileged user into clicking the malicious link, potentially enabling unauthorized configuration changes or user account modifications.
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< 11.8.0.15>= 11.9.0, < 11.9.0.8CVSS 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:L
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.
-
Determine StorageGRID version via Grid ManagerLog into the Grid Management Interface and navigate to Help > About, or inspect the version displayed on the login page or dashboardAffected if The displayed version is below 11.8.0.15, or is 11.9.0 through 11.9.0.7 (any version in the 11.9.0.x range except 11.9.0.8 and later)
-
Verify installed version via CLIIf you have administrative CLI access, run the storagegrid --version command or check /etc/storagegrid-release file if accessibleAffected if The version output matches the vulnerable ranges specified above
Your environment is affected if the installed StorageGRID version is any release prior to 11.8.0.15, or is any 11.9.0.x release prior to 11.9.0.8.
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 · scoped11.8.0.1511.9.0.8
Upgrade StorageGRID to version 11.8.0.15 or 11.9.0.8 or later. Additionally, implement URL parameter validation and output encoding on the affected endpoints to prevent reflected XSS attacks.
11.8.0.15 or later for 11.8.x line; 11.9.0.8 or later for 11.9.x line
- 1. Verify current StorageGRID version by logging into the Grid Manager and navigating to the Maintenance section or by running 'sudo storagegrid --version'
- 2. If running a version < 11.8.0.15 (11.8.x line), plan upgrade to 11.8.0.15 or later
- 3. If running a version >= 11.9.0 and < 11.9.0.8, plan upgrade to 11.9.0.8 or later
- 4. Review NetApp's StorageGRID upgrade documentation and release notes for the target version
- 5. Create a backup of the StorageGRID configuration before upgrading
- 6. Download the upgrade package from the NetApp Support site (mysupport.netapp.com)
- 7. Perform the upgrade during a scheduled maintenance window following NetApp's standard upgrade procedure
- 8. After upgrade, verify the new version is running and confirm the XSS vulnerability is addressed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26514 — 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-26514 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