dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-4999

MEDIUM · 6.3 CVSS v3.1 Published 2026-03-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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 security vulnerability has been detected in z-9527 admin up to 72aaf2dd05cf4ec2e98f390668b41e128eec5ad2. This issue affects the function uploadFile of the file /server/utils/upload.js of the component isImg Check. The manipulation of the argument fileType leads to path traversal. Remote exploitation of the attack is possible. The exploit has been disclosed publicly and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. 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 confidence

Path traversal vulnerability in the uploadFile function of z-9527 admin's /server/utils/upload.js. The isImg check can be bypassed via manipulation of the fileType argument, allowing attackers to write files to arbitrary locations on the server. This could enable remote code execution if malicious files are placed in executable locations.

MitigationImplement strict allowlist-based validation for file types using both magic byte verification and extension checking. Store uploaded files outside the webroot with non-executable permissions, and rename files to prevent direct execution.

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

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

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. Locate the z-9527 admin application
    Search the system for files or directories named 'z-9527', 'admin', or check running processes/websites for the admin panel. Common locations include /var/www/, /opt/, or within node_modules.
    Affected if z-9527 admin is installed on the system
  2. Identify the upload.js file
    Locate the file /server/utils/upload.js within the z-9527 admin installation directory. Use 'find' command or search within the project structure.
    Affected if The file /server/utils/upload.js exists in the z-9527 admin installation
  3. Check the z-9527 admin version
    Inspect package.json, VERSION file, or git tags within the z-9527 admin directory to determine the installed version. Compare against any known version ranges.
    Affected if The installed version falls within an affected range (if known) or cannot be determined to be patched
  4. Verify upload endpoint accessibility
    Check if the upload functionality is exposed via API routes. Look for routes in server.js, app.js, or route configuration files that reference '/upload' or 'uploadFile'.
    Affected if The upload endpoint is accessible without additional authentication or network restrictions
  5. Inspect the isImg validation in upload.js
    Open /server/utils/upload.js and examine the isImg function. Look for fileType argument handling and verify if extension-based validation can be bypassed via manipulation.
    Affected if The isImg check relies solely on fileType argument without proper sanitization or allowlist validation

The system is affected if z-9527 admin is installed with the vulnerable upload.js file, the upload endpoint is accessible, and the isImg check can be bypassed via fileType argument manipulation.

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

Implement strict allowlist-based validation for file types using both magic byte verification and extension checking. Store uploaded files outside the webroot with non-executable permissions, and rename files to prevent direct execution.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4999 — 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-2026-4999 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