dbcve.org
InjectionWeakness · CWE-74

CVE-2026-7699

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 flaw has been discovered in Dromara MaxKey up to 3.5.13. Affected by this issue is the function StrUtils.checkSqlInjection of the file StrUtils.java. Performing a manipulation of the argument filtersfields results in sql injection. The attack is possible to be carried out remotely. The exploit has been released to the public and may be used for attacks. 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 Dromara MaxKey up to version 3.5.13 in the StrUtils.checkSqlInjection function within StrUtils.java. The filtersfields parameter is not properly sanitized, allowing malicious SQL manipulation. The attack can be carried out remotely and public exploits are available.

MitigationSince the vendor is unresponsive, organizations should implement input validation/sanitization on the filtersfields parameter at the application layer, deploy a WAF rule to block SQL injection attempts targeting this endpoint, and consider upgrading to a patched version if available or implementing compensating controls.

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 MaxKey installation and version
    Locate the MaxKey installation directory and check for version information in deployed JAR/WAR files, version.properties, or the startup scripts (start.bat/start.sh). Look for version strings like '3.5.x' or '3.5.13' in the deployment artifacts
    Affected if The installed version is 3.5.13 or any earlier version (3.5.x, 3.5.0, etc.)
  2. Locate the vulnerable StrUtils.java file
    Search the deployed application codebase for the file StrUtils.java and verify the checkSqlInjection function exists. Check if this function is called with user-supplied input from the filtersfields parameter
    Affected if StrUtils.java with checkSqlInjection function exists and processes the filtersfields parameter without sanitization
  3. Identify filtersfields parameter usage
    Examine the application code that handles HTTP requests to find where the filtersfields parameter is received and passed to StrUtils.checkSqlInjection. Look in controller or filter classes that handle search or filtering operations
    Affected if The filtersfields parameter from HTTP requests is directly passed to the SQL injection check function without prior validation
  4. Confirm network exposure of the vulnerable endpoint
    Determine if the application endpoint that accepts the filtersfields parameter is accessible from the network. Check firewall rules, reverse proxy configurations, or application security settings
    Affected if The endpoint handling the filtersfields parameter is externally accessible or accessible to untrusted users
  5. Verify input validation is absent
    Inspect the code flow from parameter reception to the SQL check function to confirm no input validation or sanitization is applied to filtersfields before reaching StrUtils.checkSqlInjection
    Affected if No input validation or sanitization is performed on the filtersfields parameter before it is used in SQL operations

You are affected if MaxKey version 3.5.13 or earlier is installed AND the filtersfields parameter endpoint is accessible AND no additional input validation exists between the user input and the StrUtils.checkSqlInjection function

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

Since the vendor is unresponsive, organizations should implement input validation/sanitization on the filtersfields parameter at the application layer, deploy a WAF rule to block SQL injection attempts targeting this endpoint, and consider upgrading to a patched version if available or implementing compensating controls.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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