Storeonce SystemApplication · Hpe

CVE-2025-37094

CRITICAL · 9.1 CVSS v3.1 Published 2025-06-02
Fix available
A fix is available. Upgrade to 4.3.11 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
A directory traversal arbitrary file deletion vulnerability exists in HPE StoreOnce Software.

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 confidence

A directory traversal vulnerability in HPE StoreOnce Software allows attackers to use '..' path sequences to navigate outside intended directories and delete arbitrary files on the system. The critical CVSS score of 9.1 reflects the combination of traversal attack surface and the destructive impact of arbitrary file deletion.

MitigationApply vendor-provided patches immediately. If no patch is available, restrict network access to the StoreOnce management interfaces and implement additional file system ACLs to limit the impact of any traversal-based deletion attempts.

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
Storeonce SystemApplication
Affected:< 4.3.11

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify HPE StoreOnce Software version
    Access the StoreOnce management interface or use the system information command to retrieve the installed software version. Compare against the affected version range.
    Affected if Installed version is less than 4.3.11
  2. Determine if remote administrative access is enabled
    Review the StoreOnce system configuration for exposed management interfaces (HTTP/HTTPS API or web UI) that accept authenticated connections from network segments.
    Affected if Remote administrative interfaces are accessible to untrusted networks or users.
  3. Review file system audit logs for anomalous deletion patterns
    Examine system and storage audit logs for file deletion operations that target paths outside expected backup or storage directories, particularly those containing '..' sequences in the request path.
    Affected if Logs show file deletion requests with directory traversal patterns or deletions outside designated storage locations.
  4. Check for unexpected file or directory removal
    Compare current backup catalogs and storage folder structures against known-good baselines or recent backups to identify missing or deleted content.
    Affected if Files or directories are missing without legitimate administrative action.

A user is affected if their HPE StoreOnce System version is below 4.3.11 AND the administrative interface is accessible to the attacker, enabling malicious directory traversal-based file deletion.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 4.3.11 or later
Fixed in 4.3.11
Interim mitigation

Apply vendor-provided patches immediately. If no patch is available, restrict network access to the StoreOnce management interfaces and implement additional file system ACLs to limit the impact of any traversal-based deletion attempts.

Recommended fix High confidence

4.3.11

  1. Check the current version of HPE StoreOnce Software.
  2. Download the fixed version (4.3.11 or later) from the HPE support portal (support.hpe.com).
  3. Follow HPE's official upgrade procedure for StoreOnce System to install the new version.
  4. Verify that the upgrade was successful and the system is running version 4.3.11 or later.
  5. Review the release notes to confirm the vulnerability is remediated.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Storeonce System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,920.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-37094 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-37094 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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