Vulnerability report

Active exploitation observed Confirmed confidence Not in CISA KEV

CVE-2022-50992

E-cology Arbitrary File Access

Weaver Network / E-cology · affected before 10.52

Watch CVE-2022-50992 Browse KEV feed
Severity
CVSS 8.7 · High
Confidence
Confirmed
Exploit status
Observed in sensors
EPSS
0.7%
First observed
20 Jul 2026
Last observed
04 Oct 2026

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

CVE-2022-50992 is an unauthenticated vulnerability affecting Weaver Network E-cology. Weaver (Fanwei) E-cology 9.5 versions prior to 10.52 contain an arbitrary file read vulnerability in the XmlRpcServlet interface at...

Is it exploited?

Yes. Previdian sensors observed exploitation attempts with confirmed confidence. Also confirmed by third-party sources.

Who is affected?

Weaver Network / E-cology affected before 10.52.

What should we do?

Patch immediately, validate internet-facing exposure, and monitor for matching requests.

Overview

E-cology Arbitrary File Access

Weaver (Fanwei) E-cology 9.5 versions prior to 10.52 contain an arbitrary file read vulnerability in the XmlRpcServlet interface at the XML-RPC endpoint that allows unauthenticated remote attackers to read arbitrary files by supplying file paths to the WorkflowService.getAttachment and WorkflowService.LoadTemplateProp methods. Attackers can exploit these methods without authentication to retrieve sensitive files including system configuration files and database credentials from the server.

Exploitation evidence was first observed by the Shadowserver Foundation on 2022-12-14 (UTC).

Weaver Network Co., Ltd. Affected
E-cology
Before 10.52
View vendor advisory (opens in new tab)
Published
30 Apr 2026
Exploitation Reported
06 Jul 2026
Attack vector
Remote
Complexity
Low
Privileges
None
User interaction
None

CVE References

Exploitation evidence

Why Previdian marks this CVE as exploited

Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.

Exploited in the wild

The Shadowserver

Recorded 06 Jul 2026

A trusted third party reported exploitation.

Active exploitation observed

Previdian sensor

First observed 20 Jul 2026

Previdian first observed exploitation attempts targeting this vulnerability in our honeypot sensors.

Known exploited vulnerability sources

Per-source evidence links for KEV attestations are available through the Previdian Pro API.

Learn about Pro API access
Source Added
The Shadowserver First 2026-07-06 00:00 UTC
Previdian Sensors 2026-08-09 14:33 UTC

Operational indicators for this CVE are listed under Detection.

Sensor telemetry

First-party evidence of exploitation activity

Previdian sensors recorded exploitation attempts targeting this vulnerability. The cards and chart show volume, unique attackers, and daily activity.

19

Attempts observed

16

Unique attacker IPs

14

Attacker countries

AF · AT · CH · CN · FI · FR · HK · HU · IN · JP · LT · SC · US · YE

13

Sensors observed

CVE-2022-50992 exploitation attempts over the last 84 days

Daily events observed by Previdian sensors

Updated 10 Oct 2026

0
1
1
1
1
0
2
0
0
0
0
0
0
0
0
0
0
0
0
0
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1
0
0
1
0
0
0
0
0
1
1
0
0
0
0
0
0
0
1
0
1
1
0
0
1
0
0
0
1
0
0
2
0
0
0
1
0
0
0
0
0
0
19 Jul 5 Aug 22 Aug 8 Sep 10 Oct

First observed 20 Jul 2026 · Last observed 04 Oct 2026

Pro adds sensor region and window summaries. Enterprise adds raw IPs, paths, User-Agents, and payloads.

Start 14-day Pro trial

Detection

Operational artifacts and observed signals

Make the evidence actionable in scanner, SOC, and edge-control workflows.

Observed signals

Request targets
User-Agents
Callback hosts
1
8
0

Request targets and User-Agents available in Pro. Callback host details available in Enterprise.

Scanner coverage

No scanner integrations recorded yet.

Virtual patch status

No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.

Learn about virtual patches →

Attacker IP Indicators

Attacker IP indicators observed · available in Pro and Enterprise.

Sensor-derived attacker IP indicators are available to Pro and Enterprise accounts under Detection and through the Pro API.

Learn about Pro API access

Risk and context

Severity, weaknesses, and research context

CVSS v4.0

8.7 High

Potential damage if exploited. Separate from whether attackers are using it.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

EPSS

0.7%

Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.

Weaknesses

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') CWE-22

All CVSS Scores

CVSS v4.0 8.7 High

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

CVSS v3.1 7.5 High

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

Timeline

From disclosure to observed exploitation

  1. 22:04 UTC

    Indicators of compromise added (16)

    Indicators of compromise recorded

  2. 22:04 UTC

    Observed by Previdian sensors

    Evidence-backed exploitation signal

  3. 00:00 UTC

    Added to Previdian KEV Feed

    High-confidence, third-party attested exploitation

  4. 16:09 UTC

    CVE published

    Vulnerability disclosed publicly

  5. 17:34 UTC

    CVE ID reserved

    Identifier reserved by the CNA

Pro API

Automate this intelligence

Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.

Start 14-day Pro trial Read API docs
  • Evidence confidence and provenance
  • First-party sensor telemetry
  • PoC and scanner references
  • Affected versions and enrichment
  • Automation-ready JSON delivery

GET /api/v2/pro/kevs/CVE-2022-50992

Free JSON includes basic KEV fields 
{
  "cve_id": "CVE-2022-50992",
  "confidence": "Confirmed",
  "cvss_score": 8.7,
  "cvss_estimated": false,
  "epss_score": 0.00705,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": true
  },
  "sensor_telemetry": { "attempts": 19, "sensors": 13 }
}