Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach admin login endpoint remotely
-
ExploitAutomate unthrottled credential guessing
-
ImpactBrute-force weak admin password for access
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Brute-force prevention, rate limiting
|
| Exploitation Conditions | The specific prerequisite is that the litemall admin-api login endpoint (AdminAuthController) enforces no lockout, throttling, CAPTCHA, or limit on failed authentication attempts, allowing unlimited credential-guessing. Exploitation is strongly LIMITED by: high attack complexity (VulDB rates it 'difficult'); dependence on weak, default, or guessable admin credentials since the flaw only removes the brute-force barrier rather than bypassing authentication; and requires the admin-api component to be deployed and network-reachable. Impact is confined to low confidentiality with no integrity or availability effect. |
| Impact | This is a genuinely low-priority issue despite being publicly documented. The CVSS 4.0 score of 2.9 (Low) is consistent across signals: the vector (AV:N/AC:H/PR:N/UI:N) describes a network-reachable, unauthenticated weakness but with HIGH attack complexity, and VulDB explicitly notes exploitability is 'difficult.' The flaw (CWE-307, missing restriction on excessive authentication attempts) has no direct impact of its own - it only enables brute-forcing, reflected in the low single confidentiality impact (VC:L) and zero integrity/availability impact. POC status is YES (the exploit is public per VulDB), but there is NO CISA KEV listing and NO EPSS score provided, so there is no evidence of real-world exploitation - publicly available exploit code exists but must not be conflated with active exploitation. A notable nuance: the realized risk is almost entirely conditional on weak or guessable admin credentials, since the AC:H rating reflects that brute-forcing a strong password remains impractical even without rate limiting. Net: a real but minor hardening gap, not an urgent threat. |
| Exploit ScenarioDerived | An attacker reaches the litemall admin login endpoint (AdminAuthController) over the network and runs an automated password-guessing tool, which the application fails to rate-limit or lock out. Over many attempts they attempt to recover a weak or default admin credential and gain administrative access. Public exploit/POC material exists (VulDB), though the high attack complexity means success hinges on weak credentials. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 05, 2026
Unlimited credential-guessing against the linlinjava litemall admin login endpoint is possible because the application imposes no lockout, throttling, CAPTCHA, or failed-attempt limit on the AdminAuthController in the litemall-admin-api module (CWE-307), affecting versions up to and including 1.8.0. A remote, unauthenticated attacker (CVSS 4.0 vector PR:N) can repeatedly submit password guesses, but exploitation is rated difficult and high-complexity: the flaw only removes the brute-force barrier rather than bypassing authentication, so it still depends on weak, default, or guessable admin credentials and on the admin-api component being deployed and network-reachable. Publicly available exploit code exists, and the vendor has not responded to the issue report; impact is confined to low confidentiality with no integrity or availability effect, making this a genuinely low-priority issue despite the public documentation.
RemediationAI
No vendor-released patch identified at time of analysis: the maintainers were notified through issue https://github.com/linlinjava/litemall/issues/584 and, per the report, have not responded, so there is no fixed release version to upgrade to. Until a fix lands, apply compensating controls at the perimeter rather than in the application. First, place litemall-admin-api behind a reverse proxy or API gateway and enforce per-IP and per-account request throttling on the login route (for example nginx limit_req with burst handling); the trade-off is that aggressive limits can lock out legitimate administrators during normal bursts, and shared NAT egress addresses can cause collateral blocking. Second, deploy fail2ban or equivalent host-level banning keyed on repeated 401/403 responses from the login endpoint, accepting that it adds operational noise and can be evaded by slow, distributed guessing. Third, enforce a strong, unique password for every admin account and rotate any default or demo credentials shipped with the project - this is the single highest-value mitigation because the weakness only removes the guessing barrier and does not defeat a strong secret. Fourth, restrict admin-api exposure with an IP allowlist, VPN, or mTLS client certificates, with the trade-off that remote or mobile administrative access must be routed through the VPN. Finally, monitor authentication logs for high-volume failed logins against the admin login path, since absent application-level lockout the only detection signal is external. Note that account-lockout mechanisms added blindly can themselves be abused as a denial-of-service lever against known admin usernames, so prefer IP-plus-account throttling with alerting over hard lockout.
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
litemall is an open-source Java/Spring Boot e-commerce platform split into several modules, including the backend administration API exposed as litemall-admin-api. CVE-2026-105237 maps to CWE-307 (Improper Restriction of Excessive Authentication Attempts), the classic missing-anti-automation root cause: the login handling code in litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminAuthController.java accepts an unbounded number of authentication requests from the same source without counting failures, delaying responses, locking accounts, or challenging the client with a CAPTCHA. Because the weakness is an absent control rather than a flawed parsing or memory-safety primitive, there is no memory corruption, injection, or deserialization component; the affected technology stack is simply the HTTP-facing Spring MVC login handler backed by the platform's credential store. Successful guessing yields an authenticated admin session, which is the reason the confidentiality impact is scored low rather than high - the vulnerability itself exposes only the login oracle, not stored data directly. The provided data lists no CPE entries, so exact platform/version binding rests on the file path and the stated 1.8.0 ceiling rather than on NVD CPE configuration.
Know when Java 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
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P
Network-reachable unauthenticated login (AV:N/PR:N) but AC:H since brute-forcing still depends on weak credentials; only low confidentiality impact (C:L) and no integrity/availability effect.
Primary rating from Vendor (vuldb).
CVSS VectorVendor: vuldb
DescriptionCVE.org
A vulnerability was detected in linlinjava litemall up to 1.8.0. This affects an unknown part of the file litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminAuthController.java of the component Login Endpoint. The manipulation results in improper restriction of excessive authentication attempts. The attack may be performed from remote. A high complexity level is associated with this attack. It is indicated that the exploitability is difficult. The exploit is now public and may be used. The project was informed of the problem early through an issue report but has not responded yet.
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
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Oracle Java SE 7 Update 6 and earlier contains multiple sandbox bypass vulnerabilities via the ClassFinder and forName m
Remote code execution in IBM Sterling B2B Integrator, Sterling Integrator, and Tivoli Common Reporting allows unauthenti
Java Runtime Environment sandbox bypass via incorrect image channel verification in 2D component allows remote unauthent
Oracle Java SE JDK/JRE 7 and 6 Update 27 and earlier allows remote code execution with complete system compromise throug
JBoss Seam 2 in Red Hat JBoss EAP 4.3.0 fails to sanitize JBoss Expression Language inputs, allowing remote attackers to
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 update 4 and earlier, 6 up
Multiple vulnerabilities in Oracle Java 7 before Update 11 allow remote attackers to execute arbitrary code by (1) using
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 2 and earlier, 6 Up
The WLS Security component in Oracle WebLogic Server 10.3.6.0, 12.1.2.0, 12.1.3.0, and 12.2.1.0 allows remote attackers
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 7 and earlier allow
Remote unauthenticated attackers can execute arbitrary code on Adobe ColdFusion servers through Java deserialization fla
The ExceptionDelegator component in Apache Struts before 2.2.3.1 interprets parameter values as OGNL expressions during
EUVD-2026-92259
GHSA-xf6v-w5fp-chqr
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB