Skip to main content
VulnerabilityPublished

CVE-2026-7699: Dromara MaxKey · SQL Injection

Affects Dromara MaxKeySource CVE Database V5

0
Compare

Public exploit available · CVSS 5.3 Medium.

Data as of 30 Oct 2026, 20:25 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
DromaraMaxKeyAffected
  • 3.5.0 – 3.5.13
14 affected builds
Fixed in–
Mavencom.dromara/maxkeypkg:maven/com.dromara/maxkeyOther threatsAffected
  • 3.5.0 – 3.5.13
14 affected builds
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Since the vendor has not responded or released a fix, users should consider implementing application-level input validation or filtering on the filtersfields parameter to mitigate injection risks. Monitoring for unusual database queries and restricting database permissions may also reduce potential impact until an official fix is available.

Description

Dromara MaxKey versions up to 3.5.13 contain a SQL injection vulnerability in the StrUtils.checkSqlInjection function within StrUtils.java. The issue arises from improper handling of the filtersfields argument, allowing remote attackers to manipulate SQL queries. An exploit has been publicly released, but the vendor has not responded or provided a fix. The vulnerability has a medium severity rating with a CVSS score of 5.3.

References

Community reviews

Loading reviews…