# CVE-2025-8702: SQL injection in WOES Intelligent Optimization Energy Saving System

> Remote attackers can exploit SQL injection in the Historical Data Query Module to read or modify database contents.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Aug 2025
- **Updated:** 8 Aug 2025
- **Also known as:** GHSA-gm99-3cg7-mhwr

## What is CVE-2025-8702?

CVE-2025-8702 is a medium-severity SQL injection vulnerability in Wanzhou WOES Intelligent Optimization Energy Saving System, published on 7 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability classified as critical has been found in Wanzhou WOES Intelligent Optimization Energy Saving System 1.0. This affects an unknown part of the file /CommonSolution/GetVariableByOneIDNew of the component Historical Data Query Module. The manipulation of the argument ObjectID leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

It affects 1 product.


Products: Wanzhou Woes Intelligent Optimization Energy Saving System.

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

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

## Is CVE-2025-8702 being exploited?

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

## Other vulnerabilities in Wanzhou WOES Intelligent Optimization Energy Saving System

- [CVE-2025-8703](https://insights.sbomify.com/CVE-2025-8703/): SQL injection in WOES Intelligent Optimization Energy Saving System (medium 5.3)
- [CVE-2025-8704](https://insights.sbomify.com/CVE-2025-8704/): SQL injection in WOES Intelligent Optimization Energy Saving System (medium 5.3)
- [CVE-2025-8705](https://insights.sbomify.com/CVE-2025-8705/): Wanzhou WOES Intelligent Optimization Energy Saving System Energy Overview Module GetTargetConfig sql injection (medium 5.3)
- [CVE-2025-8706](https://insights.sbomify.com/CVE-2025-8706/): Wanzhou WOES Intelligent Optimization Energy Saving System Energy Overview Module CreateFunctionLog sql injection (medium 5.3)
- [CVE-2025-8701](https://insights.sbomify.com/CVE-2025-8701/): Wanzhou WOES Intelligent Optimization Energy Saving System GetPageList sql injection (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-8702 is a medium-severity SQL injection vulnerability in Wanzhou WOES Intelligent Optimization Energy Saving System, published on 7 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-8702 exists.

Affected product: Wanzhou WOES Intelligent Optimization Energy Saving System. 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-8702/ (Markdown: https://insights.sbomify.com/CVE-2025-8702/index.md)
```

## Sources

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

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