Security readout for executives and security teams
Plain-English summary
CVE-2022-50992 lets unauthenticated internet attackers read files from vulnerable Weaver E-cology servers. Sensitive configuration files or database credentials could be exposed. The issue affects E-cology 9.5 before version 10.52. Treat externally reachable instances as high priority because no login or user interaction is required.
Executive priority
Prioritize remediation for any internet-facing Weaver E-cology deployment this week, sooner if credentials or sensitive records are stored on the server. The business risk is data exposure, not direct system takeover based on the provided sources.
Technical view
The vulnerability is a CWE-22 arbitrary file read in E-cology XmlRpcServlet. The XML-RPC endpoint exposes WorkflowService.getAttachment and WorkflowService.LoadTemplateProp methods that can accept attacker-supplied file paths without authentication. CVSS v4.0 is 8.7, with network access, low complexity, no privileges, and high confidentiality impact.
Likely exposure
Organizations running Weaver E-cology 9.5 before 10.52 are likely exposed if the XML-RPC XmlRpcServlet endpoint is reachable from untrusted networks. Internet-facing deployments have the highest risk. Internal-only systems still matter because the flaw requires no authentication.
Exploitation context
The source bundle states exploitation evidence was first observed by Shadowserver on 2022-12-14 UTC. CISA KEV status is false in the provided data. Public technical writeups are referenced, so defenders should assume opportunistic probing is plausible, but ongoing active exploitation is not confirmed by KEV here.
Researcher notes
Evidence supports unauthenticated file read through XmlRpcServlet workflow methods. The provided CVE data names version 10.52 as the fixed boundary, but product version metadata is sparse. Avoid assuming broader Weaver products are affected without vendor confirmation.
Mitigation direction
- Upgrade Weaver E-cology 9.5 to version 10.52 or later, per available vendor guidance.
- Review Weaver security downloads and release notes for the exact supported remediation package.
- Restrict access to XmlRpcServlet from untrusted networks until remediation is complete.
- Rotate exposed database or application credentials if file access is suspected.
- Preserve logs before remediation if compromise assessment is needed.
Validation and detection
- Inventory Weaver E-cology instances and record exposed versions.
- Confirm whether any E-cology 9.5 instance is below 10.52.
- Check whether XmlRpcServlet is reachable externally or from broad internal networks.
- Review web access logs for suspicious XML-RPC requests to workflow service methods.
- Validate remediation by confirming the installed version and vendor patch status.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-22: 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 lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupFile 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 lookupCVE-2022-50992 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.7 (4.0)
- Known Exploited
- No
- Published
Vector: 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
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.
CVSS vector scores
1 official scoreWe 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.
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——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
8.7HighVector: 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
Source materials
- CVE List V5 sourceCVE List V5
- https://www.weaver.com.cn/cs/securityDownload.html#CVE reference · patch
- https://www.weaver.com.cn/cs/ecology_full_log.htmlCVE reference · release-notes
- https://www.cnvd.org.cn/flaw/show/CNVD-2022-43245CVE reference · third-party-advisory
- https://blog.csdn.net/qq_36618918/article/details/135104295CVE reference · technical-description, exploit
- https://blog.csdn.net/xiayu729100940/article/details/135205082CVE reference · technical-description, exploit
- https://www.vulncheck.com/advisories/weaver-e-cology-unauthenticated-arbitrary-file-read-via-xmlrpcservletCVE reference · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.