dbcve.org
InjectionWeakness · CWE-74

CVE-2026-3672

MEDIUM · 6.3 CVSS v3.1 Published 2026-03-07
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 has been found in JeecgBoot up to 3.9.1. Affected is the function isExistSqlInjectKeyword of the file /jeecg-boot/sys/api/getDictItems. Such manipulation leads to sql injection. The attack may be performed from remote. The exploit has been disclosed to the public and may be used.

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 JeecgBoot up to v3.9.1 in the /jeecg-boot/sys/api/getDictItems endpoint. The isExistSqlInjectKeyword function intended to prevent SQL injection can be bypassed, allowing remote attackers to inject malicious SQL queries via this API.

MitigationUpgrade JeecgBoot to a version beyond 3.9.1 that includes the security patch. If immediate upgrade is not feasible, temporarily disable or restrict network access to the affected API endpoint as a compensating control.

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 JeecgBoot installation
    Locate the JeecgBoot application deployment - check for jeecg-boot related WAR/JAR files, or look for the application running on Java application servers. Inspect application startup logs or banner for the product name.
    Affected if JeecgBoot is deployed in the environment
  2. Determine the installed version
    Check the version in the deployed application - common locations: pom.xml in source, version in WAR/JAR filename, jeecg.boot.version in application.properties or pom.xml, or in the JAR manifest. Compare against the affected range (up to v3.9.1).
    Affected if Version is v3.9.1 or earlier
  3. Verify the vulnerable endpoint is exposed
    Attempt to access the API endpoint /jeecg-boot/sys/api/getDictItems via HTTP request (e.g., curl http://target/jeecg-boot/sys/api/getDictItems). If the endpoint responds (even with an error), it is exposed.
    Affected if The endpoint responds and is network-accessible
  4. Check for the vulnerable function in the codebase
    If source code is available, search for the function isExistSqlInjectKeyword in the controller handling the /sys/api/getDictItems endpoint. If only binary is available, decompile the relevant class and look for this function.
    Affected if The isExistSqlInjectKeyword function exists and can be analyzed for bypass potential
  5. Confirm bypass vulnerability via testing
    Send a crafted request with SQL injection payloads to /jeecg-boot/sys/api/getDictItems (e.g., parameter values containing SQL meta-characters like quotes, unions, or comments). Observe if the isExistSqlInjectKeyword function fails to block malicious SQL constructs.
    Affected if SQL injection payloads are not blocked and produce unexpected database behavior

The environment is affected if JeecgBoot version v3.9.1 or earlier is installed and the /jeecg-boot/sys/api/getDictItems endpoint is accessible without the bypass being patched.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade JeecgBoot to a version beyond 3.9.1 that includes the security patch. If immediate upgrade is not feasible, temporarily disable or restrict network access to the affected API endpoint as a compensating control.

Recommended fix Moderate confidence

JeecgBoot version newer than 3.9.1 (check official releases for 3.9.2+)

  1. 1. Verify the current JeecgBoot version by checking the pom.xml or build configuration file
  2. 2. Check JeecgBoot's official GitHub repository (https://github.com/jeecgboot/JeecgBoot) or release notes for versions newer than 3.9.1 that address SQL injection vulnerabilities
  3. 3. If a newer stable version (such as 3.9.2 or later) is available with security fixes, upgrade the JeecgBoot dependency in pom.xml to that version
  4. 4. Rebuild and redeploy the application
  5. 5. Verify the fix by testing the /jeecg-boot/sys/api/getDictItems endpoint with typical SQL injection payloads to confirm the vulnerability is remediated
  6. 6. If no patched version is available, contact JeecgBoot vendor support for a security patch or hotfix
Caveat Review release notes for any breaking changes between 3.9.1 and the target upgrade version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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