Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privileged employee
-
DeliveryCall unannotated updateConfig endpoint
-
ExploitDisable lockout and two-factor login
-
ExecutionClear lockout records via batchDelete
-
ImpactEnable follow-on credential attacks system-wide
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires a valid authenticated session as a low-privileged SmartAdmin employee (PR:L); exploitation then needs no special product configuration because the updateConfig and loginFail batchDelete endpoints in AdminProtectController ship without the authorization annotation enforced by AdminInterceptor, so default deployments through v3.30.0 are affected. The limiting factor is the account prerequisite: an attacker must first hold or obtain ordinary employee credentials and reach the admin API over the network; there is no unauthenticated path and no user interaction is required. |
| Impact | This is a genuine but moderate-priority issue rather than an urgent crisis. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) and the description agree: exploitation is network-reachable, low-complexity, requires no user interaction, but DOES require an authenticated low-privileged employee account (PR:L) - it is not a pre-auth remote flaw. Impact is confined to integrity (VI:H) with no confidentiality or availability loss, consistent with the described ability to alter security-protection settings rather than read or destroy data. The real danger is indirect: by disabling login lockout and two-factor login, weakening password rules, and clearing lockout records, an attacker degrades the controls that protect every other account, enabling follow-on credential attacks (e.g., brute force) that would otherwise be blocked. No EPSS score, CISA KEV listing, or public exploit code is present in the supplied data, so there is no evidence of active exploitation or automatable mass exploitation; the signals point to a plausible-but-not-yet-widely-weaponized vulnerability whose severity depends heavily on how easily low-privileged accounts can be obtained in a given deployment. Note the input Tag 'Authentication Bypass' is imprecise - the CWE-862 (Missing Authorization) classification and description describe a broken authorization check, not a bypass of authentication itself; verify categorization with the vendor/NVD. |
| Exploit ScenarioDerived | A low-privileged employee (or an attacker who has phished or otherwise obtained ordinary employee credentials) logs into SmartAdmin and directly invokes the AdminProtectController updateConfig endpoint, which lacks an authorization annotation. They disable login lockout and two-factor login and weaken password complexity, then call loginFail batchDelete to erase lockout records - clearing the way for brute-force or password-spraying attacks against higher-privileged accounts. No public exploit code is identified in the provided data, though a HackMD technical writeup and a VulnCheck advisory document the endpoints involved. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
Missing authorization in SmartAdmin through 3.30.0 lets any authenticated low-privileged employee change system-wide level-3 protection settings, disabling login lockout and two-factor login, weakening password rules, and clearing existing lockout records through the unannotated updateConfig and loginFail batchDelete endpoints in AdminProtectController. The prerequisite is an ordinary employee session (CVSS PR:L, no user interaction, network-reachable admin API), so the barrier is the account rather than any special configuration, and default deployments up to v3.30.0 are impacted; no public exploit identified at time of analysis and no CISA KEV listing, and the assessed impact is integrity-only (CVSS:3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N), making this a genuine but moderate-priority issue rather than an urgent crisis. No vendor-released patch was identified at time of analysis.
RemediationAI
No vendor-released patch was identified at time of analysis, so the most direct fix is a source-level one: add the authorization annotation that AdminInterceptor expects (the check at lines 84-96 of AdminInterceptor.java) to the updateConfig method and the loginFail batchDelete handler in AdminProtectController.java, then rebuild and redeploy; adopt the vendor's patched release once it is published. Until that can be done, deploy compensating controls that target the specific gap: block or allowlist network access to the admin API surface at the VPN, reverse proxy, or firewall layer so only trusted administrator networks can reach AdminProtectController routes (trade-off: legitimate remote administrators lose access until they use the allowlisted path), and use a reverse proxy or WAF rule to reject POST requests to the protect-config update and loginFail batchDelete paths from non-admin roles while still permitting them for verified administrators (trade-off: overly broad blocking of those paths freezes legitimate protection-configuration changes, and false-positive matching can break admin workflows). Because the vulnerability is gated only on holding any employee credential (PR:L), tighten account hygiene as a secondary control: audit, disable or rotate unused and stale employee accounts, and restrict self-registration or shared logins, recognizing that this does not remove the flaw itself. Finally, since the tampering persists and is silent, monitor application logs for calls to the updateConfig and loginFail batchDelete endpoints and periodically diff the level-3 protection configuration (lockout threshold, two-factor enforcement, password policy, lockout table) against an approved baseline, re-enabling any weakened settings; log-based detection is only retrospective and will not prevent a first successful change.
Affected VersionsENISA
Affected Packages
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 admin/back-office scaffolding framework whose API is built on Java 17 and Spring Boot 3; the affected code lives in the sa-admin module of the smart-admin-api-java17-springboot3 build. Authorization is enforced centrally by AdminInterceptor, whose annotation-based check at lines 84-96 only validates permissions on controller methods that carry the expected authorization annotation; AdminProtectController at lines 55-65 exposes updateConfig and the loginFail batchDelete handler without that annotation, so the interceptor passes these requests through for any authenticated session. This is the CWE-862 missing authorization class: the endpoint exists and is reachable, but the role/permission gate is simply absent rather than bypassable. Because the target is the level-3 protection configuration, the practical effect is modification of security controls for the whole deployment (login lockout policy, two-factor login enforcement, password complexity, and the lockout record table) rather than exposure or corruption of business data. The independent assessment scores it integrity-only with unchanged scope (S:U) and no confidentiality or availability effect, which is consistent with a settings-tampering flaw whose consequences materialize later as weakened brute-force and credential-stuffing defenses rather than as immediate data loss. The linked references point to the exact vulnerable source lines, a technical writeup, and the VulnCheck advisory; no CPE identifiers were supplied in the available data.
Know when the next one hits your stack
- 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
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
Network-reachable admin API with low complexity and no user interaction, but requires an authenticated low-privileged account (PR:L); impact is integrity-only (altering security settings), so C:N/A:N.
Primary rating from Vendor (vulncheck).
CVSS VectorVendor: vulncheck
DescriptionCVE.org
SmartAdmin through 3.30.0 contains a missing authorization vulnerability in AdminProtectController that allows authenticated low-privileged employees to modify system-wide level-3 protection settings. Attackers can call the unannotated updateConfig and loginFail batchDelete endpoints to disable login lockout and two-factor login, weaken password rules, and clear lockout records.
Executive ViewAI
SmartAdmin deployments up to version 3.30.0 contain a missing authorization flaw that lets any authenticated low-privileged employee alter system-wide protection settings, including disabling login lockout and two-factor login, weakening password rules, and clearing lockout records. This creates an insider or compromised-account risk that can undermine authentication safeguards across the organization, though no public exploit identified at time of analysis and no vendor-released patch identified at time of analysis. Leadership should prioritize containment and monitoring because the integrity of account security controls is at stake, even if exploitation requires an existing employee account.
No vendor-released patch identified at time of analysis. Interim mitigations include restricting network access to the SmartAdmin admin API and AdminProtectController endpoints to trusted management networks, enforcing strict role-based access and least privilege for employee accounts, temporarily disabling or custom-authorizing the updateConfig and loginFail batchDelete endpoints for non-admin users, enforcing MFA and lockout controls at an external identity provider or gateway, and monitoring/alerting on changes to level-3 protection settings, login lockout, two-factor login, password rules, and batch lockout record deletions.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
EUVD-2026-98948
GHSA-5mw6-hjmc-5xjc
NVD
CVE.org
EPSS
Exploit-DB