dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-7468

HIGH · 7.3 CVSS v3.1 Published 2026-04-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges 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 1024-lab smart-admin up to 3.30.0. This affects an unknown function of the file /smart-admin-api/druid/index.html of the component Demo Site. The manipulation leads to improper access controls. The attack may be initiated remotely. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through an issue report but has not responded yet.

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

The Druid database connection pooling monitoring console at /smart-admin-api/druid/index.html in smart-admin up to version 3.30.0 lacks proper access controls, allowing unauthenticated remote attackers to access sensitive database monitoring information, connection pool statistics, and potentially execute SQL queries through the Druid console's built-in features.

MitigationRestrict access to the Druid console by enabling built-in authentication, applying network-level access controls (firewall/IP whitelisting), or disabling the Druid console entirely in production environments.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 smart-admin installation
    Locate the smart-admin application and determine its version by checking the project's pom.xml, package.json, or the deployed WAR/JAR file's metadata
    Affected if The installed version is 3.30.0 or lower (any version up to and including 3.30.0)
  2. Verify Druid console endpoint is reachable
    Attempt to access http://<host>:<port>/smart-admin-api/druid/index.html from an unauthenticated browser session or using curl without credentials
    Affected if The Druid monitoring console page loads successfully without requiring any login authentication
  3. Confirm Druid console is enabled in configuration
    Check the application's configuration files (typically application.yml or application.properties) for druid console settings such as druid.web.enabled=true or similar Druid-related configuration
    Affected if Druid console is explicitly enabled in the configuration (not disabled via druid.web.enabled=false or equivalent setting)
  4. Check for authentication on Druid console features
    Once the console is accessible, attempt to access the SQL execution feature or view connection pool details without providing any authentication credentials
    Affected if Sensitive monitoring data (connection pool statistics, database credentials exposure, SQL query execution interface) is visible or accessible without authentication

You are affected if running smart-admin version 3.30.0 or lower AND the Druid console at /smart-admin-api/druid/index.html is accessible without authentication, which exposes sensitive database monitoring information and potentially allows SQL execution.

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

Restrict access to the Druid console by enabling built-in authentication, applying network-level access controls (firewall/IP whitelisting), or disabling the Druid console entirely in production environments.

Recommended fix Moderate confidence

3.30.1 (check github.com/1024-lab/smart-admin for official releases)

  1. 1. Restrict network access to the Druid console at /smart-admin-api/druid/index.html using firewall rules or network segmentation to allow only trusted IPs
  2. 2. Disable the Druid monitoring console in production environments by setting druid.stat.view.enabled=false or removing the druid-web dependency
  3. 3. If authentication is required, configure Druid security settings including username and password in the application configuration
  4. 4. Alternatively, upgrade to smart-admin version 3.30.1 or later if a fixed release becomes available
  5. 5. Verify the Druid console is no longer publicly accessible after applying mitigations

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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