Skip to main content

SmartAdmin CVE-2026-108923

| EUVDEUVD-2026-97783 LOW
Improper Access Control (CWE-284)
2026-10-12 VulDB GHSA-wwvh-6vc7-p2p2
2.1
CVSS 4.0 · Vendor: VulDB
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as low-privilege user
  2. Delivery
    Send request to /support/config/queryByKey
  3. Exploit
    Manipulate configKey parameter
  4. Execution
    Bypass access control check
  5. Impact
    Read restricted configuration data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Access control enforcement
MITRE ATT&CK

1 technique across 1 tactic: Defense Evasion

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires a valid authenticated session with at least low-level privileges (CVSS PR:L) against an application built on 1024-lab smart-admin ≤3.30.0, specifically reaching the Support Config Query component's /support/config/queryByKey endpoint and manipulating the configKey argument. No user interaction or non-default configuration is indicated (UI:N, AC:L, AT:N), so any account that can reach the Support Config function is sufficient. Limiting factors: the attacker must already possess credentials (this is not unauthenticated), impact is confined to Low confidentiality/integrity/availability with no scope change, and exposure depends on the SmartAdmin-based deployment being network-reachable to the attacker.

Impact

This is a genuine but modest-priority issue, not a top-tier emergency. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) scores 5.3 (MEDIUM) and indicates a network-reachable, low-complexity flaw that nonetheless requires some level of authentication (PR:L), so it is not a pre-auth remote compromise. CWE-284 (improper access control) combined with the endpoint name /support/config/queryByKey points to a broken-access-control / horizontal-or-vertical privilege issue where an authenticated low-privilege user can read configuration they should not reach. Exploitation signals are mixed: a public exploit/PoC is referenced (GitHub issue #137) and VulDB marks exploit maturity E:P (proof-of-concept), but there is NO CISA KEV listing and NO EPSS score was provided, so there is no evidence of widespread or active exploitation - treat the PoC as available-but-not-confirmed-weaponized. The impacts in the input vector (VC:L/VI:L/VA:L) are each only Low and no scope change occurs (SC/SI/SA:N), consistent with limited data exposure rather than full system takeover. Note a conflict worth verifying: the input Tags label this 'Authentication Bypass,' but PR:L and CWE-284 describe access control abuse by an already-authenticated user, not an authentication bypass - verify the exact privilege boundary with the project. Net: a real low-to-medium access-control bug in a niche open-source product that the vendor has not yet acknowledged; schedule a fix but it does not warrant emergency response absent broader deployment or escalation evidence.

Exploit ScenarioDerived

An authenticated low-privilege user of a SmartAdmin-based application sends a crafted request to /support/config/queryByKey, manipulating the configKey parameter to retrieve configuration entries that should be restricted to administrators. A public proof-of-concept tied to the project's GitHub issue tracker (issue #137) exists, lowering the effort to reproduce, though the low attack complexity is offset by the requirement for a valid account.

Monitor Track and reassess. Why: LOW severity (CVSS 0.1-3.9).
No patch listed yet 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 12, 2026

Improper access control in 1024-lab SmartAdmin 3.30.0 and earlier lets any authenticated low-privilege user read configuration values they should not see by manipulating the configKey argument of the /support/config/queryByKey endpoint. The endpoint is remotely reachable and publicly available exploit code exists (a GitHub issue containing the proof of concept), but the flaw is not listed in CISA KEV and the project has not responded to the report. With a CVSS 4.0 base score of 5.3 and only low confidentiality/integrity/availability impact, this is a genuine but modest-priority issue rather than a top-tier emergency.

RemediationAI

No vendor-released patch identified at time of analysis: the maintainers were notified through issue 137 and have not responded according to VulDB entry https://vuldb.com/vuln/416747, so no fixed SmartAdmin version is confirmed in the available data. Until an upstream fix is published, the most effective compensating control is to add an explicit authorization check on /support/config/queryByKey so that only administrative roles can invoke it - the trade-off is that any legitimate non-admin support or customer-service screens that depend on this endpoint will stop working, so role mappings must be reviewed first. Where source changes are not feasible, block or return 403 for the path at the reverse proxy or API gateway for non-admin sessions, accepting that this is a coarse control that can be bypassed if the application is reachable directly rather than through the proxy. Additional hardening: enforce server-side whitelisting of permitted configKey values (side effect: legitimate dynamic keys must be enumerated and maintained), avoid storing credentials or secrets in support configuration records since this endpoint can expose them, and log/alert on repeated or sequential configKey values from low-privilege accounts to detect enumeration. Track the upstream repository at https://github.com/1024-lab/smart-admin/ and the VulDB entry for a patched release, and upgrade as soon as a version beyond 3.30.0 that addresses the authorization gap is available.

Affected VersionsENISA

smart-admin 3.1
smart-admin 3.20
smart-admin 3.23
smart-admin 3.12
smart-admin 3.2
smart-admin 3.30.0
smart-admin 3.10
smart-admin 3.26
smart-admin 3.22
smart-admin 3.13
smart-admin 3.6
smart-admin 3.17
smart-admin 3.27
smart-admin 3.9
smart-admin 3.28
smart-admin 3.0
smart-admin 3.19
smart-admin 3.25
smart-admin 3.16
smart-admin 3.15
smart-admin 3.24
smart-admin 3.8
smart-admin 3.5
smart-admin 3.11
smart-admin 3.29
smart-admin 3.18
smart-admin 3.14
smart-admin 3.7
smart-admin 3.21
smart-admin 3.3
smart-admin 3.4

Affected Packages

euvd smart_admin no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

SmartAdmin (1024-lab/smart-admin) is an open-source Java/Spring Boot administration framework, typically paired with a Vue front end, that is widely used as a base for building internal management systems. The affected component is the Support Config Query function exposed at /support/config/queryByKey, which returns a stored configuration record for a caller-supplied key. The root cause class is CWE-284 (Improper Access Control): the handler does not verify that the caller is authorized for the requested configuration before returning it, so the configKey value can be manipulated to read records the session should not access. Per the assessed CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L) and our independent CVSS 3.1 assessment (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N), a valid authenticated account with at least low-level privileges is required; this is not unauthenticated access, and no user interaction or non-default configuration is needed. Note that third-party tagging labels this an "Authentication Bypass," but the authoritative assessment treats it as missing authorization on an authenticated endpoint, i.e. a privilege-escalation-in-read issue confined to low impact with no scope change, rather than a pre-auth bypass.

Know when Smart Admin gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulDB) PRIMARY 2.1 MEDIUM
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
vuln.today AI 4.3 MEDIUM

Network-reachable queryByKey read endpoint abusable by an authenticated low-privilege user (PR:L, AC:L); improper access control primarily exposes configuration data, so C:L with I:N/A:N.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
Low
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

3
Severity Changed
Oct 12, 2026 - 20:22 NVD
MEDIUM LOW
CVSS changed
Oct 12, 2026 - 20:22 NVD
5.3 (MEDIUM) 2.1 (LOW)
CVE Published
Oct 12, 2026 - 19:15 cve.org
MEDIUM 5.3

DescriptionCVE.org

A vulnerability was determined in 1024-lab smart-admin up to 3.30.0. Affected by this vulnerability is an unknown functionality of the file /support/config/queryByKey of the component Support Config Query. Executing a manipulation of the argument configKey can lead to improper access controls. The attack can be executed remotely. The exploit has been publicly disclosed and may be utilized. The project was informed of the problem early through an issue report but has not responded yet.

Threat Intelligence Overview

EPSS Score
0.4%
Top 73% exploitable
Prevalence
Low
niche open-source Chinese rapid-development admin framework, limited production footprint
Exploit
POC
Public exploit code exists
Data Quality
6 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity LOW
CISA KEV No
Public POC Yes
EPSS 0.4%
Patch available No
Active threat No
Deciding rule
LOW severity (CVSS 0.1-3.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Low
Technical Impact
Partial

Priority Score

30
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +10
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy