# CVE-2022-3947: eolinker goku_lite list sql injection

> Remote attackers can exploit SQL injection in the list endpoint to read or modify database contents.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **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:** 11 Nov 2022
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-37j8-vpm4-fh2c

## What is CVE-2022-3947?

CVE-2022-3947 is a medium-severity SQL injection vulnerability in eolinker goku_lite, published on 11 Nov 2022. 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 eolinker goku_lite. This affects an unknown part of the file /balance/service/list. The manipulation of the argument route/keyword leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-213453 was assigned to this vulnerability.

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

## Which versions are affected by CVE-2022-3947?

It affects 1 product.


Products: Eolink Goku Lite.

## How do I fix CVE-2022-3947?

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

## Is CVE-2022-3947 being exploited?

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

## Other vulnerabilities in eolinker goku_lite

- [CVE-2022-3948](https://insights.sbomify.com/CVE-2022-3948/): eolinker goku_lite getList sql injection (medium 6.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-3947 and fix it if it is affected.

What it is: CVE-2022-3947 is a medium-severity SQL injection vulnerability in eolinker goku_lite, published on 11 Nov 2022. 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-2022-3947 exists.

Affected product: eolinker goku_lite. 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-2022-3947/ (Markdown: https://insights.sbomify.com/CVE-2022-3947/index.md)
```

## Sources

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

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