Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with high-privilege account
-
ExploitSend crafted request to ParamController initPassword
-
ExecutionBypass authorization check on system parameter
-
ImpactModify init password configuration
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization verification
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 an authenticated session with high privileges (CVSS PR:H) against the SpringBlade Parameter Submit Management feature, specifically the ParamController endpoint that handles the initPassword argument. The flaw is an improper-authorization check (CWE-285) on that parameter, so the limiting factor is that an attacker must already possess elevated access to the SpringBlade backend; no unauthenticated or low-privilege path is indicated. No user interaction is required (UI:N), and no non-default configuration is specified in the available data, but impact is constrained to LOW across confidentiality, integrity, and availability. |
| Impact | This is a low-priority issue despite being remotely reachable. The vendor-supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L) scores only 2.0, driven primarily by PR:H - the attacker must already hold high privileges in the SpringBlade system before touching the vulnerable initPassword parameter - and by uniformly LOW impact (VC:L/VI:L/VA:L) with no scope change. Exploitation signals are mixed but weak: publicly available exploit code exists (POC=YES) and the CVSS includes E:P (proof-of-concept exploit maturity), but there is NO CISA KEV listing and NO EPSS score was provided, so there is no evidence of active or widespread exploitation. The single intelligence source is VulDB, and the 'exploit' reference is simply a GitHub issue report (#41) that the project has not yet acknowledged - this is a reporter-disclosed issue rather than confirmed weaponization. Net: a genuine authorization flaw (CWE-285) but a low-real-risk one, gated behind existing privileged access and causing only limited impact. The 'Authentication Bypass' tag overstates the issue - the underlying weakness is improper authorization requiring an already-authenticated high-privilege actor, not an authentication bypass; verify with the issue report before treating it as a pre-auth bypass. |
| Exploit ScenarioDerived | An authenticated user holding high privileges in a SpringBlade deployment sends a crafted request to the Parameter Submit Management endpoint (ParamController) and manipulates the initPassword argument, which is not properly authorization-checked, to alter the system's initial-password configuration. A proof-of-concept is publicly available via the project's GitHub issue tracker, but exploitation yields only limited confidentiality, integrity, and availability impact and requires pre-existing privileged access. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 06, 2026
Improper authorization in the SpringBlade Java microservice framework (all versions up to 5.0.1) lets an authenticated user holding high privileges manipulate the initPassword argument exposed by the Parameter Submit Management controller (ParamController) and change system parameters they should not be able to control. The endpoint is remotely reachable, but exploitation requires an existing elevated session with no user interaction, and the assessed impact is LOW across confidentiality, integrity and availability (CVSS 3.1 AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L). Publicly available exploit code exists and the project has not responded to the issue report, so no vendor-released patch is available at time of analysis.
RemediationAI
No vendor-released patch identified at time of analysis: the project was informed through issue #41 but has not responded, so the fix must currently come from compensating controls while tracking https://github.com/chillzhuang/SpringBlade/ for an upstream commit or tagged release that adds the missing authorization check in ParamController.java. Operationally, restrict the SpringBlade management API (the blade-system parameter endpoints) to the smallest possible set of administrator roles and, where feasible, to trusted management networks or VPN rather than the public internet, accepting that this breaks legitimate remote admin workflows. Enforce separation of duties so that the permission tied to the parameter-submit operation, including initPassword, is not granted to ordinary or departmental accounts, and audit role assignments for over-broad grants. Add an explicit server-side authorization assertion on the parameter update path before applying initPassword values, and log and alert on changes to that parameter, with the trade-off of extra development effort and possible false positives in audit alerting. Because exploit code is publicly available and only authenticated high-privilege sessions are required, rotate any administrative credentials that may have been used by untrusted operators and review recent parameter and credential changes for tampering. Monitor the GitHub repository and VulDB entries https://vuldb.com/vuln/413641/cti and https://vuldb.com/cve/CVE-2026-105610 for the release of an official fix and apply it as soon as a fixed version is published.
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
SpringBlade is a Java/Spring Boot-based microservice application framework maintained by chillzhuang, with a modular layout in which blade-service/blade-system hosts the system management domain. The affected code is the controller class blade-service/blade-system/src/main/java/org/springblade/system/controller/ParamController.java, part of the Parameter Submit Management component, which exposes an operation taking an initPassword argument. Because the server fails to perform a correct authorization check on that operation (CWE-285, Improper Authorization), a caller who already holds a high-privilege session can supply the parameter and reach functionality intended to be restricted, instead of being rejected with a 403. The CVSS 4.0 vector records AV:N/AC:L/AT:N while requiring PR:H and no user interaction, with LOW-level confidentiality, integrity and availability impact and an E:P exploit-maturity flag, which matches the public proof-of-concept referenced in the project's GitHub issue. The CPE entry cpe:2.3:a:chillzhuang:springblade:*:*:*:*:*:*:*:* confirms that the framework itself, rather than a downstream application, is the affected component. The underlying weakness class is authorization logic, not memory corruption or injection, so exploitation is limited to actions the mis-scoped role can already reach over the management API.
Know when Springblade 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:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
Remotely reachable (AV:N) but the authorization flaw is reachable only by an already high-privileged user (PR:H), with limited impact across C/I/A and no scope change.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
Lifecycle Timeline
3DescriptionCVE.org
A vulnerability was found in chillzhuang SpringBlade up to 5.0.1. The impacted element is an unknown function of the file blade-service/blade-system/src/main/java/org/springblade/system/controller/ParamController.java of the component Parameter Submit Management. The manipulation of the argument initPassword results in improper authorization. It is possible to launch the attack remotely. The exploit has been made public and could 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
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Springblade
View allAccess control bypass in SpringBlade v4.5.0 importUser function allows low-privileged users to import sensitive user dat
SpringBlade v3.2.0 and below was discovered to contain a SQL injection vulnerability via the component customSqlSegment.
The DAO/DTO implementation in SpringBlade through 2.7.1 allows SQL Injection in an ORDER BY clause. Rated critical sever
Privilege escalation in SpringBlade 2.7.3 through 3.5.0 lets authenticated low-privilege users forge admin JWT tokens us
An issue discovered in SpringBlade 3.7.1 allows attackers to obtain sensitive information via crafted GET request to api
An issue in SpringBlade v.3.7.0 and before allows a remote attacker to escalate privileges via the lack of permissions c
SpringBlade v4.5.0 has an access control flaw in authRoutes allowing low-privileged users to escalate to admin through t
In SpringBlade V3.6.0 when executing SQL query, the parameters submitted by the user are not wrapped in quotation marks,
A vulnerability classified as critical has been found in chillzhuang SpringBlade 4.1.0. Rated medium severity (CVSS 5.3)
SpringBlade <=V3.6.0 is vulnerable to Incorrect Access Control due to incorrect configuration in the default gateway res
Authorization bypass in SpringBlade through 5.0.2 lets attackers read other users' account information by supplying an a
Improper authorization in SpringBlade up to 5.0.1 allows an authenticated remote user to access role or user detail reco
EUVD-2026-92932
GHSA-2xgm-59p5-jc7j
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB