# CVE-2024-4457: Remote Code Execution via JDBC User Store Configuration in Multiple WSO2 Products Allows Arbitrary Code Execution

> Attackers can execute arbitrary code on WSO2 servers by exploiting improper input validation in the JDBC user store configuration.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-4m8f-7prf-f25h

## What is CVE-2024-4457?

CVE-2024-4457 is a critical command injection vulnerability in WSO2 API Manager, published on 18 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Management Console fails to properly validate input related to the configuration of JDBC user stores. This weakness allows an attacker to supply specially crafted input that can lead to the execution of arbitrary code on the affected server.

Successful exploitation of this vulnerability enables an attacker to execute arbitrary code on the server with the privileges of the WSO2 product. This could lead to a full compromise of the system.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2024-4457?


## How do I fix CVE-2024-4457?

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

## Is CVE-2024-4457 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-4457 and fix it if it is affected.

What it is: CVE-2024-4457 is a critical command injection vulnerability in WSO2 API Manager, published on 18 Oct 2026. 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-2024-4457 in the wild and no public exploit code.

Affected product: WSO2 API Manager. 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-2024-4457/ (Markdown: https://insights.sbomify.com/CVE-2024-4457/index.md)
```

## Sources

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

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