CVE-2025-5158
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 vulnerability was found in H3C SecCenter SMP-E1114P02 up to 20250513. It has been declared as problematic. This vulnerability affects the function downloadSoftware of the file /cfgFile/downloadSoftware. The manipulation of the argument filename leads to path traversal. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceA path traversal vulnerability exists in the downloadSoftware function of H3C SecCenter SMP-E1114P02. Attackers can manipulate the filename argument in /cfgFile/downloadSoftware to access files outside the intended directory, potentially reading sensitive system files.
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<= 20250513CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 H3C SecCenter SMP product versionAccess the SMP management interface or check system information page to locate the firmware/build version. It should display as a date code like 20250513 or earlier.Affected if The installed version is H3C SecCenter SMP-E1114P02 with a build date of 20250513 or earlier.
-
Confirm the vulnerable endpoint existsAttempt to access or probe the URI /cfgFile/downloadSoftware on the SMP management web interface. This endpoint is typically accessible via HTTP/HTTPS.Affected if The endpoint responds (even with an error) indicating the downloadSoftware function is present.
-
Verify the downloadSoftware function is enabledCheck the SMP configuration or feature flags to confirm the file download/downloadSoftware capability is active. This may be visible in the web interface menus or in the backend configuration.Affected if The downloadSoftware function is listed as available or enabled in the SMP configuration.
-
Test for path traversal vulnerability (optional and cautious)If authorized, send a crafted request to /cfgFile/downloadSoftware with a filename parameter containing traversal sequences such as ../../../../etc/passwd or ../../../../windows/win.ini to attempt reading system files outside the intended directory.Affected if The response returns content from files outside the intended download directory, confirming the path traversal is exploitable.
You are affected if you are running H3C SecCenter SMP-E1114P02 with version/build date 20250513 or earlier, the /cfgFile/downloadSoftware endpoint is accessible, and path traversal sequences in the filename parameter successfully read arbitrary files.
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 strict input validation and sanitization for the filename parameter, ensuring paths are restricted to allowed directories and preventing traversal sequences (../)
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5158 — 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-5158 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