CVE-2021-26587
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 · uneditedA potential DOM-based Cross Site Scripting security vulnerability has been identified in HPE StoreOnce. The vulnerability could be remotely exploited to cause an elevation of privilege leading to partial impact to confidentiality, availability, and integrity. HPE has made the following software update - HPE StoreOnce 4.3.0, to resolve the vulnerability in HPE StoreOnce.
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 confidenceA DOM-based Cross Site Scripting (XSS) vulnerability in HPE StoreOnce allows remote attackers to inject malicious scripts into web pages viewed by other users. This can lead to session hijacking, credential theft, or elevation of privileges through the execution of attacker-controlled JavaScript in the victim's browser context.
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.2.3<= 4.2.3<= 4.2.3<= 4.2.3<= 4.2.3<= 4.2.3CVSS 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
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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.
-
Identify the HPE StoreOnce modelAccess the StoreOnce management web interface and navigate to the System Information or About page to confirm the model is one of: 5200, 5650, 5250, 3640, 3620, or VSA 4TBAffected if The model is any of these six listed models
-
Check the firmware versionIn the web management interface, locate the firmware version displayed in System Information, About, or Diagnostics. Alternatively, access the CLI and run 'show system' or 'version' command to retrieve the firmware versionAffected if The firmware version is 4.2.3 or earlier (any version <= 4.2.3)
-
Verify web interface accessibilityConfirm the StoreOnce management web interface (HTTPS on port 5481 or similar) is accessible from a browserAffected if The web interface is exposed and reachable, as the DOM-based XSS payload would be injected through web pages served by the management interface
You are affected if your HPE StoreOnce model is one of the six listed models AND your firmware version is 4.2.3 or earlier AND the management web interface is accessible.
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 · scopedApply HPE StoreOnce version 4.3.0 or later, which contains the vendor patch for this vulnerability. Until patching is possible, restrict network access to the StoreOnce management interface to trusted users only.
HPE StoreOnce 4.3.0
- 1. Navigate to HPE support portal (support.hpe.com) and locate the HPE StoreOnce firmware download section
- 2. Download the HPE StoreOnce 4.3.0 firmware update package for your specific StoreOnce model
- 3. Follow HPE's standard firmware upgrade procedure: access the StoreOnce GUI, navigate to Administration > Maintenance > Firmware Update
- 4. Upload the downloaded firmware file and initiate the upgrade process
- 5. Allow the system to reboot and complete the installation
- 6. Verify the firmware version shows 4.3.0 in the StoreOnce GUI to confirm successful update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-26587 — 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-2021-26587 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