dbcve.org
E CologyApplication · Weaver

CVE-2023-3793

CRITICAL · 9.8 CVSS v3.1 Published 2023-07-20
Fix available
A fix is available. Upgrade to 10.58.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability was found in Weaver e-cology. It has been rated as critical. This issue affects some unknown processing of the file filelFileDownloadForOutDoc.class of the component HTTP POST Request Handler. The manipulation of the argument fileid with the input 1+WAITFOR+DELAY leads to sql injection. Upgrading to version 10.58.0 is able to address this issue. It is recommended to upgrade the affected component. The identifier VDB-235061 was assigned to this vulnerability.

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 confidence

A critical SQL injection vulnerability exists in Weaver e-cology's HTTP POST Request Handler (filelFileDownloadForOutDoc.class). The vulnerability is exploitable via the 'fileid' parameter using time-based SQL injection techniques (WAITFOR DELAY), allowing remote attackers to execute arbitrary SQL commands against the database.

MitigationUpgrade Weaver e-cology to version 10.58.0 or later. As this is a critical SQL injection with CVSS 9.8, prioritize this upgrade immediately and consider temporary network-level restrictions until patching is complete.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
E CologyApplication
Affected:< 10.58.0

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
High
Availability
High

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Weaver e-cology installation
    Check for Weaver e-cology web application in the application server's webapps directory (e.g., /webapps/ecology/ or similar paths depending on application server). Look for the characteristic folder structure or check HTTP response headers for 'ecology' or 'weaver' server signatures.
    Affected if Weaver e-cology is not present in the environment.
  2. Determine installed version
    Locate the version manifest or version file within the e-cology installation directory. Common locations include VERSION.txt, version.properties in the webroot or WEB-INF folder, or check the about/page within the application.
    Affected if The installed version is less than 10.58.0 (e.g., 10.57.0, 10.56.x, earlier releases).
  3. Verify vulnerable component exists
    Check for the presence of the class file 'filelFileDownloadForOutDoc.class' within the compiled web application. This is typically located under WEB-INF/classes/ in the e-cology deployment directory.
    Affected if The vulnerable class file exists in the deployment.
  4. Check external exposure of the vulnerable endpoint
    Identify if the HTTP POST endpoint handling the filelFileDownloadForOutDoc request is accessible externally. This typically involves the /weavering/ or similar request routing paths. Use web server access logs to identify requests to this handler.
    Affected if The endpoint is accessible from untrusted networks and accepts the 'fileid' parameter.

If Weaver e-cology is installed with a version lower than 10.58.0 and the filelFileDownloadForOutDoc endpoint is exposed, the environment is affected by this SQL injection vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 10.58.0 or later
Fixed in 10.58.0
Interim mitigation

Upgrade Weaver e-cology to version 10.58.0 or later. As this is a critical SQL injection with CVSS 9.8, prioritize this upgrade immediately and consider temporary network-level restrictions until patching is complete.

Recommended fix High confidence

10.58.0

  1. 1. Back up the current E Cology installation and database before starting the upgrade process
  2. 2. Obtain the fixed version 10.58.0 from the official Weaver e-cology vendor or authorized distribution channel
  3. 3. Review the official upgrade documentation for E Cology to understand the upgrade procedure specific to your deployment
  4. 4. Apply the upgrade to your E Cology installation, following the vendor's recommended upgrade steps
  5. 5. After upgrading, verify that the filelFileDownloadForOutDoc.class component has been updated and the SQL injection vulnerability is resolved
  6. 6. Test the file download functionality for out-documents to confirm normal operation
  7. 7. Monitor logs for any SQL injection attempts or errors
Caveat Review vendor release notes for any configuration or behavioral changes between your current version and 10.58.0 before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in E Cology Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-3793 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-3793 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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