CVE-2022-50992
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 · uneditedWeaver (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).
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 confidenceWeaver E-cology 9.5 versions before 10.52 contain an arbitrary file read vulnerability in the XmlRpcServlet XML-RPC endpoint. Unauthenticated attackers can exploit WorkflowService.getAttachment and WorkflowService.LoadTemplateProp methods by supplying file paths to read sensitive system files including configuration files and database credentials.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm E-cology installation and versionLocate the E-cology installation directory and check the version file or banner. Common locations include the root web directory. Look for a version manifest, build file, or login page footer that displays the version number.Affected if The version is E-cology 9.5 and is earlier than 10.52 (e.g., 9.5.0 through 10.51)
-
Identify XmlRpcServlet endpoint availabilityCheck the web.xml deployment descriptor for the XmlRpcServlet mapping. This is typically found in the WEB-INF directory of the E-cology web application. Look for servlet definitions with 'XmlRpc' or 'xmlrpc' in the name.Affected if The XmlRpcServlet is defined and mapped to a URL pattern such as /xmlrpc or /services/xmlrpc
-
Verify WorkflowService exposureInspect the deployed web application for the WorkflowService class or servlet that handles the WorkflowService XML-RPC methods. This may be visible in the application configuration or by checking the exposed web service endpoints.Affected if The WorkflowService class is deployed and exposes the getAttachment and LoadTemplateProp methods via XML-RPC
-
Confirm unauthenticated access to endpointAttempt to access the XmlRpcServlet URL endpoint without authentication. This is the endpoint that handles the XML-RPC requests for WorkflowService methods. Check if the server responds to unauthenticated requests.Affected if The XmlRpcServlet endpoint is accessible without authentication (no login required)
-
Check for sensitive file access patterns in logsReview server access and application logs for unusual requests to the XmlRpcServlet endpoint that contain file path parameters. Look for patterns indicating attempts to read configuration or system files.Affected if There are logged requests to the XmlRpc endpoint with file path parameters pointing to sensitive locations such as config files or credential stores
A user is affected if they are running Weaver E-cology version 9.5 before 10.52 with the XmlRpcServlet endpoint exposed and accessible without authentication.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to E-cology version 10.52 or later; alternatively, disable or restrict access to the XmlRpcServlet endpoint and implement strict input validation on file path parameters.
Weaver E-cology 10.52 or later
- 1. Identify current E-cology version by checking the application or consulting vendor documentation
- 2. Download Weaver E-cology version 10.52 or later from the official Weaver (Fanwei) vendor website or authorized distribution channel
- 3. Review the official upgrade guide and release notes for version 10.52
- 4. Perform a backup of the current E-cology installation including database and configuration files
- 5. Apply the upgrade to version 10.52 following vendor-provided installation instructions
- 6. Verify the XmlRpcServlet interface no longer allows unauthorized file access by testing the WorkflowService.getAttachment and WorkflowService.LoadTemplateProp methods with restricted paths
- 7. Confirm the upgrade was successful and the application functions normally
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-50992 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-50992 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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