# CVE-2022-50993: Weaver E-office < 10.0_20221201 Unauthenticated Arbitrary File Read via XmlRpcServlet

> Unauthenticated attackers can upload malicious PHP files to achieve remote code execution on Weaver E-office servers.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Apr 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-g99j-cq2q-3xrv

## What is CVE-2022-50993?

CVE-2022-50993 is a critical vulnerability in Weaver Network Co., Ltd. E-office, published on 30 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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).

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2022-50993?


## How do I fix CVE-2022-50993?

No fix has been published for CVE-2022-50993 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-50993 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-50993 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-50993 and fix it if it is affected.

What it is: CVE-2022-50993 is a critical vulnerability in Weaver Network Co., Ltd. E-office, published on 30 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-50993 exists.

Affected product: Weaver Network Co., Ltd. E-office. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-50993/ (Markdown: https://insights.sbomify.com/CVE-2022-50993/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-50993
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-50993
- OSV: https://osv.dev/vulnerability/CVE-2022-50993

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-50993/
Summaries are generated and may contain mistakes; the official description above is the record.