dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2022-50993

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-30
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
Weaver (Fanwei) E-office versions prior to 10.0_20221201 contain an unauthenticated arbitrary file upload vulnerability in the OfficeServer.php endpoint that allows remote attackers to upload malicious files by sending multipart POST requests with arbitrary filenames and disguised content types. Attackers can upload PHP webshells to the Document directory and execute them via HTTP GET requests to achieve remote code execution as the web server user. Exploitation evidence was first observed by the Shadowserver Foundation on 2022-10-10 (UTC).

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

Weaver E-office versions before 10.0_20221201 have an unauthenticated arbitrary file upload vulnerability in the OfficeServer.php endpoint. Attackers can send multipart POST requests with arbitrary filenames and content types to upload malicious PHP files to the Document directory, then execute them via HTTP GET requests to achieve remote code execution as the web server user.

MitigationUpgrade to Weaver E-office version 10.0_20221201 or later to patch the arbitrary file upload vulnerability. If immediate patching is not possible, restrict access to OfficeServer.php or disable file upload functionality in the Document directory until the patch can be applied.

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 Weaver E-office installation and version
    Locate the main E-office installation directory and look for version information in configuration files, headers, or the application itself. Common locations include the web root or a dedicated E-office directory.
    Affected if The installed version is lower than 10.0_20221201 and the application is Weaver E-office.
  2. Verify OfficeServer.php exists and is web-accessible
    Check if OfficeServer.php file exists in the web-accessible directory, typically found in the E-office web root or /api/ path.
    Affected if OfficeServer.php exists and is reachable via HTTP/HTTPS from the web.
  3. Confirm Document directory is web-accessible
    Check for a 'Document' or 'documents' directory within the web-accessible E-office installation that can store uploaded files.
    Affected if The Document directory exists and is accessible via HTTP/HTTPS (uploaded files can be served).
  4. Check if uploaded files can be executed
    Test whether the web server will execute PHP files in the Document directory by attempting to access an existing legitimate file or checking server configuration.
    Affected if The web server executes PHP or other script files in the Document directory rather than serving them as plain text.
  5. Compare version to affected range
    Review the identified version against the affected range: versions before 10.0_20221201 are vulnerable.
    Affected if The installed version is any version prior to 10.0_20221201.

You are affected if Weaver E-office version is below 10.0_20221201 AND OfficeServer.php is web-accessible AND the Document directory allows web-accessible file uploads that can be executed as scripts.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Weaver E-office version 10.0_20221201 or later to patch the arbitrary file upload vulnerability. If immediate patching is not possible, restrict access to OfficeServer.php or disable file upload functionality in the Document directory until the patch can be applied.

Recommended fix High confidence

Weaver E-office version 10.0_20221201 or later

  1. Obtain the official Weaver E-office version 10.0_20221201 or later from the vendor's authorized distribution channel
  2. Take a complete backup of the current E-office installation including the webroot, database, and configuration files
  3. Deploy version 10.0_20221201 in a staging environment to verify compatibility with existing workflows
  4. Apply the upgrade to the production environment following vendor documentation
  5. Verify that the OfficeServer.php endpoint no longer accepts unauthenticated file uploads
  6. Confirm that existing legitimate file upload functionality works correctly
  7. Monitor logs for any suspicious POST requests to OfficeServer.php indicating continued exploitation attempts

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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