CVE-2023-47458
CriticalCVSS 9.8Exploitation Probability (EPSS)
Low risk46th percentile - higher than 46% of all known CVEs
Summary
In SpringBlade version 3.7.0 and earlier, a missing permission control framework allows a remote attacker to escalate privileges.
Risk Assessment
An attacker can gain unauthorized access to administrative functions and sensitive data, leading to a breach of system confidentiality and integrity.
Recommendation
Immediately update SpringBlade to the latest version that includes access control fixes and implement authorization mechanisms at the application level.
Other vulnerabilities in SpringBlade
See all- CVE-2026-36765High
An XXE vulnerability in the /designer/loadReport endpoint of SpringBlade v4.8.0 allows authenticated attackers to execute arbitrary code via injecting a crafted payload.
- CVE-2026-56100High
SpringBlade versions from 2.7.3 up to but not including 5.0.0 contain a privilege escalation vulnerability that allows authenticated attackers to create system administrator accounts by sending crafted POST requests to an unprotected internal Feign user-creation endpoint exposed via @RestController without authorization checks. Attackers can exploit the gateway's authentication filter, which only validates JWT parsing without verifying user roles or caller identity, and leverage a hardcoded JWT signing key embedded in publicly available JARs to forge tokens and escalate privileges from a low-privilege user to administrator, enabling cross-tenant data pollution and persistent backdoor access.
Original NVD description (English source)
An issue in SpringBlade v.3.7.0 and before allows a remote attacker to escalate privileges via the lack of permissions control framework.

