CVE-2024-8023: A vulnerability classified as critical has been found in chillzhuang SpringBlade 4.1.0

Q: How do I fix CVE-2024-8023?

springblade: upgrade to newer than 4.1.0. Exact commands for each OS are on this page.

Q: Is CVE-2024-8023 being exploited?

CVE-2024-8023 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-8023 affect?

CVE-2024-8023 affects springblade. Severity is medium (CVSS 6.3). A vulnerability classified as critical has been found in chillzhuang SpringBlade 4.1.0. Affected is an unknown function of the file /api/blade-system/menu/list?updatexml. The manipulation leads to sql injection. It is possible to launch the

Q: How urgent is CVE-2024-8023?

Priority 40/100. Public exploit reference

This month

MEDIUM 6.3UPGRADE

CVE-2024-8023 is a medium-severity flaw (CVSS 6.3) affecting springblade. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A vulnerability classified as critical has been found in chillzhuang SpringBlade 4.1.0. Affected is an unknown function of the file /api/blade-system/menu/list?updatexml. The manipulation leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	6.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.6% (top 50%)
CISA exploited list	No
Weakness	CWE-89
Published	2024-08-21
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: bladex

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-08-21 00:15 UTCPublished CVE record published
2026-06-17 08:21 UTCUpdated Record last modified

bladex springblade UPGRADE

Affected: <= 4.1.0

Fixed in: newer than 4.1.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy springblade || rpm -q springblade || springblade --version

2. UPGRADE to newer than 4.1.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade springblade

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade springblade

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-8023?

springblade: upgrade to newer than 4.1.0. Exact commands for each OS are on this page.

Is CVE-2024-8023 being exploited?

CVE-2024-8023 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-8023 affect?

CVE-2024-8023 affects springblade. Severity is medium (CVSS 6.3). A vulnerability classified as critical has been found in chillzhuang SpringBlade 4.1.0. Affected is an unknown function of the file /api/blade-system/menu/list?updatexml. The manipulation leads to sql injection. It is possible to launch the

How urgent is CVE-2024-8023?

Priority 40/100. Public exploit reference

Related CVEs

CVE-2025-70983 CRITICAL 9.9 DOWNGRADE Incorrect access control in the authRoutes function of SpringBlade v4.5.0 allows attackers with low-level priv
CVE-2025-70982 CRITICAL 9.9 DOWNGRADE Incorrect access control in the importUser function of SpringBlade v4.5.0 allows attackers with low-level priv
CVE-2024-33332 HIGH 7.5 DOWNGRADE An issue discovered in SpringBlade 3.7.1 allows attackers to obtain sensitive information via crafted GET requ

References

← Back to latest CVEs