CVE-2025-5162
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, which was classified as critical, has been found in H3C SecCenter SMP-E1114P02 up to 20250513. Affected by this issue is some unknown functionality of the file /safeEvent/importFile/. The manipulation of the argument logGeneralFile/logGeneralFile_2 leads to unrestricted upload. The attack may 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 · high confidenceUnrestricted file upload vulnerability in H3C SecCenter SMP-E1114P02's /safeEvent/importFile/ endpoint allows remote attackers to upload arbitrary files via the logGeneralFile/logGeneralFile_2 parameters, potentially achieving remote code execution. CVSS 9.8 indicates critical severity with no authentication required.
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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm H3C SecCenter SMP installationIdentify if H3C SecCenter SMP-E1114P02 is running in your environment by checking running services, web server logs, or network scans for the product. Look for HTTP services on common ports that respond with H3C SecCenter headers or pages.Affected if The product H3C SecCenter SMP-E1114P02 is present in the environment
-
Check installed versionLocate the SMP management interface or system information page, typically accessed via the web console. Look for the firmware or software version displayed, which should show a date code like 20250513 or similar.Affected if The displayed version is 20250513 or any version dated earlier (lower numerical date code)
-
Verify endpoint accessibilitySend an HTTP request to the path /safeEvent/importFile/ on the SMP server (e.g., GET https://<target>/safeEvent/importFile/). Check if the endpoint responds or accepts requests, indicating it is exposed.Affected if The /safeEvent/importFile/ endpoint is reachable and does not return a 404 or access denied error
-
Test unauthenticated access to upload endpointAttempt a HEAD or OPTIONS request to /safeEvent/importFile/ without providing authentication credentials. Observe whether the server accepts the request without requiring login.Affected if The endpoint accepts requests without requiring authentication (no redirect to login, no 401/403 response)
-
Check network exposureReview firewall rules, ACLs, or network segmentation to determine if the SMP web interface is exposed to untrusted networks or the internet. Use nmap or similar to check if the web port is open externally.Affected if The SMP web interface is accessible from untrusted networks or the internet
A user is affected if H3C SecCenter SMP-E1114P02 version 20250513 or earlier is installed and the /safeEvent/importFile/ endpoint is accessible without authentication, especially from untrusted networks.
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 file type validation (allowlist approach), verify file content/magic bytes not just extensions, enforce authentication/authorization on the endpoint, and consider network segmentation/disabling the feature until vendor patch is available.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5162 — 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-5162 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