Unrestricted File UploadWeakness · CWE-434

CVE-2025-4556

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-12
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
The web management interface of Okcat Parking Management Platform from ZONG YU has an Arbitrary File Upload vulnerability, allowing unauthenticated remote attackers to upload and execute web shell backdoors, thereby enabling arbitrary code execution on the server.

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

Okcat Parking Management Platform from ZONG YU contains an arbitrary file upload vulnerability in its web management interface. Unauthenticated remote attackers can upload malicious files (web shells) to the server and execute them, achieving arbitrary code execution on the underlying system.

MitigationImplement strict file upload validation including authentication requirements, file type whitelist validation, file content inspection, store uploads outside webroot, and disable script execution in upload directories.

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. Confirm Okcat Parking Management Platform is installed
    Inspect running services or application directories for Okcat Parking or ZONG YU parking management software. Check web server configurations for parking management related virtual hosts or applications.
    Affected if The system is running Okcat Parking Management Platform from ZONG YU
  2. Determine the installed version
    Check application version files, about pages, or administrative interfaces for the software version number. Compare against any available version information from the vendor.
    Affected if The installed version is unknown or falls within the affected version range for this vulnerability
  3. Verify web management interface is exposed
    Check network accessible services to confirm the Okcat web management interface is reachable via HTTP/HTTPS from network locations.
    Affected if The web management interface is accessible over the network without authentication restrictions
  4. Identify file upload functionality
    Locate the file upload feature in the web management interface by examining upload forms, endpoints, or API paths related to document/image/file uploads.
    Affected if File upload functionality exists and is accessible in the web interface
  5. Check upload endpoint authentication
    Test access to the file upload endpoint without providing credentials to determine if authentication is required. Inspect session handling and access control configurations.
    Affected if File upload endpoint accepts requests without requiring valid authentication credentials
  6. Inspect upload directory configuration
    Examine web server and application configuration to determine where uploaded files are stored relative to the web root and whether script execution permissions are restricted in those directories.
    Affected if Uploaded files are stored within the web root and script execution is permitted in the upload directory

The system is affected if it runs Okcat Parking Management Platform with an upload feature accessible without authentication and stores uploads in a web-accessible location where script execution is allowed.

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 file upload validation including authentication requirements, file type whitelist validation, file content inspection, store uploads outside webroot, and disable script execution in upload directories.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-4556 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-4556 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