CVE-2025-5161
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 classified as problematic was found in H3C SecCenter SMP-E1114P02 up to 20250513. Affected by this vulnerability is the function operationDailyOut of the file /safeEvent/download. The manipulation of the argument filename leads to path traversal. The attack can be launched 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 · moderate confidencePath traversal vulnerability in H3C SecCenter SMP-E1114P02 allows remote attackers to access arbitrary files via the filename parameter in the /safeEvent/download endpoint, specifically the operationDailyOut function. The vulnerability stems from insufficient input validation allowing directory traversal sequences (e.g., ../../) in the filename argument.
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 H3C SecCenter SMP installationLocate the H3C SecCenter SMP web application. Check for the presence of the /safeEvent/download endpoint by accessing it directly via HTTP request (e.g., GET /safeEvent/download).Affected if The /safeEvent/download endpoint is accessible and responds to requests.
-
Confirm product versionCheck the installed version of H3C SecCenter SMP-E1114P02. This is typically displayed in the product about page, in the system information section of the admin interface, or in version files within the application directory.Affected if The installed version is 20250513 or earlier.
-
Test the vulnerable parameterSend a crafted request to /safeEvent/download with a directory traversal payload in the filename parameter (e.g., ../../etc/passwd or ../../../../windows/win.ini). Observe whether the application returns file contents from outside the intended directory.Affected if The application returns content from files outside the intended directory, indicating the path traversal is successful.
-
Check access controls on download endpointReview the application's configuration or web server logs to verify whether authentication is required for the /safeEvent/download endpoint. Attempt the traversal test both with and without valid credentials.Affected if The endpoint is accessible without authentication or with low-privilege user credentials.
If the H3C SecCenter SMP-E1114P02 version is 20250513 or earlier and the /safeEvent/download endpoint responds to requests with directory traversal payloads in the filename parameter, the environment is affected by CVE-2025-5161.
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 with allowlisting for the filename parameter, use basename() to strip directory components, and ensure the application restricts file access to intended directories only.
- Consultation4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5161 — 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-5161 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