# CVE-2025-34038: Weaver E-cology SQL Injection

> Unauthenticated attackers can execute arbitrary SQL queries via the getdata.jsp endpoint to expose sensitive data like administrator password hashes.

- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jun 2025
- **Updated:** 14 May 2026
- **Also known as:** GHSA-3464-wq8g-r9gp

## What is CVE-2025-34038?

CVE-2025-34038 is a high-severity SQL injection vulnerability in Weaver E-cology, published on 24 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A SQL injection vulnerability exists in Weaver E-cology 8.0 via the getdata.jsp endpoint. The application directly passes unsanitized user input from the sql parameter into a database query within the getSelectAllIds(sql, type) method, reachable through the cmd=getSelectAllId workflow in the AjaxManager. This allows unauthenticated attackers to execute arbitrary SQL queries, potentially exposing sensitive data such as administrator password hashes. Exploitation evidence was observed by the Shadowserver Foundation on 2025-02-05 UTC.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2025-34038?

It affects 1 product.


Products: Weaver E-Cology.

## How do I fix CVE-2025-34038?

No fix has been published for CVE-2025-34038 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-34038 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-34038 exists.

Public exploit code:

- Fanwei e-cology - SQL Injection (nuclei): http/cves/2025/CVE-2025-34038.yaml

## Other vulnerabilities in Weaver E-cology

- [CVE-2024-48069](https://insights.sbomify.com/CVE-2024-48069/): Race condition in n/a (critical 9.8)
- [CVE-2024-48070](https://insights.sbomify.com/CVE-2024-48070/): Code injection in n/a (critical 9.8)
- [CVE-2024-48072](https://insights.sbomify.com/CVE-2024-48072/): SQL injection in n/a (critical 9.8)
- [CVE-2023-51892](https://insights.sbomify.com/CVE-2023-51892/): Code injection in n/a (critical 9.8)
- [CVE-2026-22679](https://insights.sbomify.com/CVE-2026-22679/): Weaver E-cology 10.0 Unauthenticated RCE via dubboApi Debug Endpoint (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-34038 and fix it if it is affected.

What it is: CVE-2025-34038 is a high-severity SQL injection vulnerability in Weaver E-cology, published on 24 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-34038 exists.

Affected product: Weaver E-cology. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-34038/ (Markdown: https://insights.sbomify.com/CVE-2025-34038/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-34038
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-34038
- OSV: https://osv.dev/vulnerability/CVE-2025-34038

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-34038/
Summaries are generated and may contain mistakes; the official description above is the record.
