LiveActive security incident?Get immediate response
CVE Record

CVE-2022-40050: ZFile v4.1.1 was discovered to contain an arbitrary file upload vulnerability via the component /file/uploa...

ZFile v4.1.1 was discovered to contain an arbitrary file upload vulnerability via the component /file/upload/1.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2022-40050 is a critical arbitrary file upload issue reported in ZFile v4.1.1. An unauthenticated network attacker may be able to upload files through /file/upload/1, creating risk of data theft, content tampering, or service disruption. The public record is sparse, so confirm whether ZFile is present before escalating operational action.

Executive priority

Prioritize rapid exposure confirmation. If ZFile v4.1.1 is externally reachable, treat remediation as urgent because the reported flaw is unauthenticated, network-accessible, and rated critical.

Technical view

The CVE record describes CWE-434 arbitrary file upload in ZFile v4.1.1 via /file/upload/1. CVSS 3.1 is 9.8 with network access, low complexity, no privileges, and no user interaction. The source bundle does not provide CPEs, fixed versions, detailed exploit conditions, or vendor mitigation guidance.

Likely exposure

Exposure is most likely where ZFile v4.1.1 is internet-accessible or reachable by untrusted users. The CVE affected-product metadata is incomplete, so asset inventory and version confirmation are required.

Exploitation context

The bundle does not show CISA KEV listing or cite active exploitation. Treat exploitation status as unconfirmed, while recognizing the CVSS vector indicates a potentially severe unauthenticated network attack surface.

Researcher notes

Evidence is limited to the CVE metadata and one public reference. The record names ZFile v4.1.1 and /file/upload/1 but lacks reproducible details, affected CPEs, patch information, and confirmed exploitation. Avoid assuming broader version impact without vendor evidence.

Mitigation direction

  • Inventory all ZFile deployments and identify any running v4.1.1.
  • Check ZFile vendor or project guidance for fixed versions or official mitigations.
  • Restrict public access to /file/upload/1 where operationally possible.
  • Require authentication and strict upload controls if the endpoint must remain available.
  • Monitor upload directories and web logs for suspicious file activity.

Validation and detection

  • Confirm whether ZFile is deployed and record the exact version.
  • Review routing or proxy configuration for exposure of /file/upload/1.
  • Inspect access logs for unexpected requests to the upload endpoint.
  • Verify file upload controls enforce type, size, storage, and execution restrictions.
  • Document patch status or compensating controls for each affected asset.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-434: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-40050 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2022-40050Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-434 · source CWE mapping

Unrestricted Upload of File with Dangerous Type

Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.