# CVE-2026-7678: YunaiV yudao-cloud GoViewDataServiceImpl.java getDataBySQL sql injection

> Remote attackers can exploit SQL injection in the yudao-cloud reporting service 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:** 3 May 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-7hx2-hqrg-qcwc

## What is CVE-2026-7678?

CVE-2026-7678 is a medium-severity SQL injection vulnerability in YunaiV yudao-cloud, published on 3 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was identified in YunaiV yudao-cloud up to 2026.01. This affects the function getDataBySQL of the file yudao-module-report-biz/src/main/java/io/github/ruoyi/report/service/impl/GoViewDataServiceImpl.java. Such manipulation leads to sql injection. It is possible to launch the attack remotely. The exploit is publicly available and might be used. The vendor explains: "[T]he SQL execution feature and existing report:go-view-data:get-by-sql functional permission remain. We are not adding a super-administrator restriction, default-off switch or independent-datasource enforcement in this batch. SQL access granted through that permission must be limited to trusted roles and appropriate database privileges; this item is not reported as patched."

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-2026-7678?


## How do I fix CVE-2026-7678?

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

## Is CVE-2026-7678 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-7678 and fix it if it is affected.

What it is: CVE-2026-7678 is a medium-severity SQL injection vulnerability in YunaiV yudao-cloud, published on 3 May 2026. 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-2026-7678 exists.

Affected product: YunaiV yudao-cloud. 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-2026-7678/ (Markdown: https://insights.sbomify.com/CVE-2026-7678/index.md)
```

## Sources

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

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