# CVE-2024-4412: Expression Language Injection via User Input in Multiple WSO2 Products Permits Arbitrary Operations

> Administrators can inject malicious Expression Language code into WSO2 products, potentially executing arbitrary operations within the deployment.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-f6jh-7mqr-5h2p

## What is CVE-2024-4412?

CVE-2024-4412 is a low-severity code injection vulnerability in WSO2 API Manager, published on 19 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The software accepts user-supplied data without sufficient validation, allowing for the injection of malicious Expression Language (EL) code. This can lead to the execution of arbitrary operations within the affected deployment.

Exploitation of this vulnerability requires administrator privileges. The impact is minimal as EL usage is restricted to certain read operations.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2024-4412 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-4412 is a low-severity code injection vulnerability in WSO2 API Manager, published on 19 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-4412 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-4412/ (Markdown: https://insights.sbomify.com/CVE-2024-4412/index.md)
```

## Sources

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

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