dbcve.org
E CologyApplication · Weaver

CVE-2026-22679

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

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
Weaver (Fanwei) E-cology 10.0 versions prior to 20260312 contain an unauthenticated remote code execution vulnerability in the /papi/esearch/data/devops/dubboApi/debug/method endpoint that allows attackers to execute arbitrary commands by invoking exposed debug functionality. Attackers can craft POST requests with attacker-controlled interfaceName and methodName parameters to reach command-execution helpers and achieve arbitrary command execution on the system. Exploitation evidence was first observed by the Shadowserver Foundation on 2026-03-31 (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 confidence

Weaver E-cology 10.0 versions prior to 20260312 contain an unauthenticated remote code execution vulnerability in the /papi/esearch/data/devops/dubboApi/debug/method endpoint. Attackers can send POST requests with attacker-controlled interfaceName and methodName parameters to invoke exposed debug functionality that leads to arbitrary command execution on the system. This is a pre-authentication RCE with CVSS 9.8 that has been observed being exploited in the wild.

MitigationApply vendor patch version 20260312 or later to all affected E-cology 10.0 instances; as an interim measure, block or restrict access to /papi/esearch/data/devops/dubboApi/debug/* endpoints at the network perimeter (WAF/firewall).

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:< 20260312

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 if Weaver E-cology 10.0 is installed
    Locate the E-cology installation directory and look for version files or check the about/info page typically found at /wui/main.jsp or similar paths within the web application
    Affected if The product is present and no version can be determined or version is earlier than 20260312
  2. Determine the installed E-cology version
    Check version manifests, build files, or the system information page within the E-cology web interface. Compare the version string to the 20260312 baseline
    Affected if The installed version is any build prior to 20260312 (e.g., 2025.x, earlier 2026 builds, or unversioned installations)
  3. Verify the vulnerable endpoint exists
    Attempt to access or enumerate the path /papi/esearch/data/devops/dubboApi/debug/method via HTTP request or check web server configuration for this route mapping
    Affected if The endpoint /papi/esearch/data/devops/dubboApi/debug/method is present and responds to requests
  4. Confirm network accessibility of the debug endpoint
    Check firewall, WAF, or reverse proxy rules to determine if the /papi/esearch/data/devops/dubboApi/debug/* path is exposed to unauthenticated external access
    Affected if The endpoint is reachable from untrusted networks without authentication

A user is affected if Weaver E-cology 10.0 is installed with any version prior to 20260312 AND the /papi/esearch/data/devops/dubboApi/debug/method endpoint is accessible to unauthenticated requestors.

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 20260312 or later
Fixed in 20260312
Vendor patch www.weaver.com.cn →
Interim mitigation

Apply vendor patch version 20260312 or later to all affected E-cology 10.0 instances; as an interim measure, block or restrict access to /papi/esearch/data/devops/dubboApi/debug/* endpoints at the network perimeter (WAF/firewall).

Recommended fix High confidence

E-cology 10.0 version 20260312 or later

  1. 1. Navigate to the official Weaver support portal at https://www.weaver.com.cn/cs/securityDownload.html
  2. 2. Locate the security patch or update for E-cology 10.0 addressing CVE-2026-22679
  3. 3. Download the update package for version 20260312 or later
  4. 4. Apply the update following Weaver's standard upgrade procedure for E-cology
  5. 5. Verify the patch was applied successfully by checking the E-cology version information
  6. 6. Confirm the /papi/esearch/data/devops/dubboApi/debug/method endpoint is no longer accessible without authentication
Caveat Standard E-cology upgrade considerations apply - test in staging first, backup database, review release notes for any configuration changes

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

Fix this in E Cology Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22679 — 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-2026-22679 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