dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2023-28814

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Some versions of Hikvision's iSecure Center Product have an improper file upload control vulnerability. Due to the improper verification of file to be uploaded, attackers may upload malicious files to the server. iSecure Center is software released for China's domestic market only, with no overseas release.

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

Hikvision's iSecure Center software contains an improper file upload vulnerability (CWE-434) allowing unauthenticated attackers to upload malicious files to the server due to insufficient validation of uploaded file types, contents, or metadata. This critical flaw (CVSS 9.8) can enable remote code execution if uploaded files are subsequently executed by the server.

MitigationApply vendor-provided patches from Hikvision immediately; if no patch exists, implement compensating controls such as restricting upload functionality to authenticated, authorized users only, storing uploads outside webroot, disabling script execution on upload directories, and implementing strict file type/content validation at the application layer.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
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 checks

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

  1. Identify iSecure Center installation
    Look for Hikvision iSecure Center installation directories (commonly in C:\Program Files\Hikvision\iSecure Center or /opt/hikvision/isecurecenter) and check for the iSecure Center service running on the host.
    Affected if iSecure Center software is installed and running on the server.
  2. Determine installed version
    Check the version of iSecure Center by examining the software's About or Version information, typically found in the installation directory or via the web management interface (usually port 443 or 8443).
    Affected if The installed version has not been patched and falls within the affected (unpatched) version range.
  3. Verify upload functionality exposure
    Determine if the file upload endpoint is accessible without authentication. This typically involves checking if the web interface allows unauthenticated access to upload features or by reviewing access control configuration files in the installation directory.
    Affected if The file upload functionality is accessible to unauthenticated (unauthenticated) users on the network.
  4. Inspect file upload validation settings
    Review the application's configuration files (often in the conf or config subdirectory) for settings related to file type validation, content inspection, or upload restrictions. Look for parameters controlling allowed file extensions, MIME types, or file size limits.
    Affected if File type/content validation is weak, missing, or disabled (for example, no extension blocklist or allowlist, no content-type checking, or no file signature validation).
  5. Check network exposure
    Determine if the iSecure Center web interface (ports 80/443 or custom ports) is exposed to the internet or an untrusted network by reviewing firewall rules and network ACLs.
    Affected if The iSecure Center web portal is reachable from untrusted networks without VPN or authentication proxy.

You are affected if Hikvision iSecure Center is installed with a vulnerable (unpatched) version AND the file upload functionality is accessible to unauthenticated users with weak or missing validation controls.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-provided patches from Hikvision immediately; if no patch exists, implement compensating controls such as restricting upload functionality to authenticated, authorized users only, storing uploads outside webroot, disabling script execution on upload directories, and implementing strict file type/content validation at the application layer.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-28814 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2023-28814 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