dbcve.org
InjectionWeakness · CWE-74

CVE-2026-7678

MEDIUM · 6.3 CVSS v3.1 Published 2026-05-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
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 was contacted early about this disclosure but did not respond in any way.

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 · moderate confidence

SQL injection vulnerability in the getDataBySQL function within GoViewDataServiceImpl.java of the yudao-cloud reporting module (yudao-module-report-biz). The function directly processes SQL input without proper parameterization or sanitization, allowing an attacker to manipulate SQL queries. The vulnerability is exploitable remotely and public exploits are available.

MitigationReplace direct SQL execution with parameterized queries or prepared statements, implement strict input validation on all user-supplied parameters, and apply least-privilege database accounts to limit impact of potential injection.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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 yudao-module-report-biz is deployed
    Search for the file GoViewDataServiceImpl.java in your codebase or check if the yudao-module-report-biz module is included in your project dependencies (pom.xml, build.gradle, or deployed JARs)
    Affected if The module yudao-module-report-biz is present in the environment
  2. Determine the yudao-cloud version
    Check your project version (pom.xml, build.gradle, or application properties) and compare it against any known affected version ranges for the reporting module
    Affected if The installed version falls within the affected version range of yudao-cloud reporting module
  3. Verify the getDataBySQL function is accessible
    Review the codebase or API endpoints to confirm the getDataBySQL method in GoViewDataServiceImpl.java is exposed as a web service, REST endpoint, or API that accepts user input
    Affected if The getDataBySQL function is exposed via an API or endpoint that accepts external input
  4. Inspect SQL query handling in the vulnerable function
    Locate GoViewDataServiceImpl.java and examine the getDataBySQL function to verify it constructs SQL queries by concatenating user-supplied input directly without using parameterized queries or prepared statements
    Affected if The code shows direct string concatenation or unsanitized input being used in SQL queries within getDataSQL
  5. Check database account privileges
    Review the database connection configuration used by the reporting module to determine if the application database account follows least-privilege principles
    Affected if The database account has excessive privileges (such as DROP, CREATE, or administrative permissions) beyond what the reporting module requires

The environment is affected if yudao-module-report-biz is deployed, the installed version is within the affected range, and the getDataBySQL function is exposed to untrusted input without parameterized queries.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace direct SQL execution with parameterized queries or prepared statements, implement strict input validation on all user-supplied parameters, and apply least-privilege database accounts to limit impact of potential injection.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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