Unauthenticated privilege escalation via missing authorization
Published Jan 2, 2024 · Updated Jul 9, 2026
Missing authorization in BladeX SpringBlade 3.7.0 and earlier allows remote attackers to escalate privileges via network requests. The public CVE record describes only an absent permissions-control framework and does not identify an endpoint, function, or authorization check. No authentication or user interaction is required, and successful exploitation grants elevated access with confidentiality, integrity, and availability consequences.
Summary
What happened
Missing authorization in BladeX SpringBlade 3.7.0 and earlier allows remote attackers to escalate privileges via network requests. The public CVE record describes only an absent permissions-control framework and does not identify an endpoint, function, or authorization check. No authentication or user interaction is required, and successful exploitation grants elevated access with confidentiality, integrity, and availability consequences.
The record
- CVE
- CVE-2023-47458
- Published
- Jan 2, 2024
- Updated
- Jul 9, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-862, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 2, 2024CVE publishedPublication date reported by the CVE source.
- Jul 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo