Skip to content
Web

CVE-2022-50993

9.3
Critical
EPSS 0.77%May 1, 2026

Unauthenticated file upload leads to remote code execution via webshell on Weaver E-office web app.

common questions

Is CVE-2022-50993 being exploited?

Not confirmed. CVE-2022-50993 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.77% probability of exploitation in the next 30 days.

How severe is CVE-2022-50993?

CVE-2022-50993 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2022-50993?

Not known from our data. No patch reference has been recorded for CVE-2022-50993, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2022-50993 affect?

CVE-2022-50993 affects Weaver E-office <= 10.0_20221201. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2022-50993?

Patch to fixed release; if unavailable, disable uploads and restrict PHP execution in upload dir

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Weaver E-office <= 10.0_20221201
impact

Remote code execution via unauthenticated file upload; PHP webshells executed as web server user.

action required

Immediate action required

affected versions
Weaver Network Co., Ltd. E-office
  • affected< 10.0_20221201

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free