# CVE-2023-47458: Missing authorization in n/a

> Remote attackers can escalate privileges in SpringBlade due to missing permission controls, requiring immediate upgrade.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jan 2024
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-89vh-9hfj-x469

## What is CVE-2023-47458?

CVE-2023-47458 is a critical missing authorization vulnerability in n/a, published on 2 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in SpringBlade v.3.7.0 and before allows a remote attacker to escalate privileges via the lack of permissions control framework.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2023-47458?

It affects 1 product.


Products: Bladex Springblade.

## How do I fix CVE-2023-47458?

No fix has been published for CVE-2023-47458 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-47458 being exploited?

There is no known exploitation of CVE-2023-47458 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2025-70982](https://insights.sbomify.com/CVE-2025-70982/): Missing authorization in n/a (critical 9.9)
- [CVE-2025-70983](https://insights.sbomify.com/CVE-2025-70983/): Privilege escalation in n/a (critical 9.9)
- [CVE-2023-40787](https://insights.sbomify.com/CVE-2023-40787/): SpringBlade vulnerable to SQL injection (critical 9.8)
- [CVE-2022-27360](https://insights.sbomify.com/CVE-2022-27360/): SQL injection in n/a (critical 9.8)
- [CVE-2020-16165](https://insights.sbomify.com/CVE-2020-16165/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-47458 and fix it if it is affected.

What it is: CVE-2023-47458 is a critical missing authorization vulnerability in n/a, published on 2 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-47458 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-47458/ (Markdown: https://insights.sbomify.com/CVE-2023-47458/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-47458
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-47458
- OSV: https://osv.dev/vulnerability/CVE-2023-47458

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-47458/
Summaries are generated and may contain mistakes; the official description above is the record.