dbcve.org
InjectionWeakness · CWE-74

CVE-2026-7672

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 security vulnerability has been detected in youlaitech youlai-boot up to 2.21.1. This affects the function getUserList of the file src/main/java/com/youlai/boot/system/controller/UserController.java of the component Users Endpoint. Such manipulation of the argument order leads to sql injection. The attack may be launched remotely. The exploit has been disclosed publicly and may 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 · high confidence

SQL injection vulnerability in youlai-boot UserController.java's getUserList function. The function constructs SQL queries using user-supplied input without proper parameterization, where manipulating the argument order allows injection of malicious SQL code. This is a medium-severity remote vulnerability in the user management endpoint.

MitigationImplement prepared statements/parameterized queries for all database operations in getUserList. Validate and sanitize all user inputs before using them in SQL construction. If no patched version exists, consider upgrading to latest release or applying input validation controls at the application boundary.

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 youlai-boot installation
    Locate the youlai-boot application directory or JAR/WAR file in your environment. Check for project files containing 'youlai-boot' in the path or build configuration.
    Affected if The application uses youlai-boot framework and contains the vulnerable UserController component.
  2. Locate UserController.java
    Search for the file UserController.java in the project source code, typically under src/main/java path, and identify the getUserList function within it.
    Affected if The getUserList function exists in UserController.java and handles user-supplied input in SQL queries.
  3. Inspect getUserList for SQL construction
    Open UserController.java and examine the getUserList method. Look for SQL query construction that uses string concatenation or string formatting with user-provided parameters (request parameters, path variables, or headers).
    Affected if The function builds SQL queries by concatenating or formatting user input directly into the query string without using parameterized queries or prepared statements.
  4. Check endpoint accessibility
    Verify that the user management endpoint (typically /user or /users path handled by getUserList) is exposed and reachable from the network. Check application routing configuration and deployed WAR/JAR configuration.
    Affected if The endpoint is accessible remotely without authentication or with weak authentication, allowing attacker-supplied input to reach the vulnerable function.
  5. Review database layer for parameterization
    Inspect the data access layer (DAO/Repository) called by getUserList. Check if database operations use PreparedStatement with bound parameters or if raw SQL strings are passed from the controller.
    Affected if The SQL query constructed in getUserList is passed directly to the database without parameter binding, allowing SQL injection payloads to be executed.

A user is affected if youlai-boot is deployed, the getUserList function in UserController.java uses string concatenation to build SQL queries with user input, and the endpoint is accessible without proper input sanitization.

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

Implement prepared statements/parameterized queries for all database operations in getUserList. Validate and sanitize all user inputs before using them in SQL construction. If no patched version exists, consider upgrading to latest release or applying input validation controls at the application boundary.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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