An improper access control vulnerability in 1024-lab smart-admin allows unauthenticated remote attackers to gain unauthorized access to system database information and sessions.

This is an improper access control flaw (CWE-284) residing in the /smart-admin-api/druid/index.html endpoint, where the application fails to enforce authentication checks. An unauthenticated remote attacker can access the Druid monitoring interface to view sensitive SQL queries and active user sessions.

The exposure of SQL statements and session data poses a severe risk of information disclosure and potential account takeover. With access to valid session tokens, an attacker may elevate their privileges to gain full administrative control over the backend, leading to complete system compromise. Given the CVSS score of 7.3, this represents a high-severity risk that demands immediate attention to prevent unauthorized data exfiltration.

Immediate Action: As no official patch is currently available from the vendor, you must immediately restrict network access to the /smart-admin-api/druid/ index path using a firewall or reverse proxy configuration to prevent public access.

Proactive Monitoring: Review web access logs for any requests directed to the /smart-admin-api/druid/index.html endpoint and monitor for suspicious session activity or unauthorized database queries.

Compensating Controls: Implement an authentication layer at the Web Application Firewall (WAF) or ingress controller level to require valid credentials before allowing traffic to reach the Druid interface.

Public Exploit Available: Yes, a published proof-of-concept exists as documented in the GitHub issue report linked in the vulnerability references.

The absence of a vendor-supplied patch makes this vulnerability particularly dangerous for organizations currently running the affected versions of smart-admin. Administrators should treat this as an urgent priority by implementing strict network-level access controls to the Druid interface immediately. Continue to monitor the vendor GitHub repository for future security updates and apply them as soon as they become available to permanently resolve the underlying access control failure.