# CVE-2024-5683: Remote Code Execution in Next4Biz's BPM

> Attackers can execute arbitrary code remotely via a code injection flaw in Next4Biz BPM, requiring an upgrade to the latest version.

- **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:** 24 Jun 2024
- **Updated:** 3 Jun 2026
- **Also known as:** GHSA-4mv5-vqcp-r46r

## What is CVE-2024-5683?

CVE-2024-5683 is a critical code injection vulnerability in Next4Biz CRM & BPM Software Business Process Manangement (BPM), published on 24 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper Control of Generation of Code ('Code Injection') vulnerability in Next4Biz CRM & BPM Software Business Process Manangement (BPM) allows Remote Code Inclusion.

This issue affects Business Process Manangement (BPM): from 6.6.4.4 before 6.6.4.5.

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

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


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

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

## Is CVE-2024-5683 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-5683 is a critical code injection vulnerability in Next4Biz CRM & BPM Software Business Process Manangement (BPM), published on 24 Jun 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-2024-5683 in the wild and no public exploit code.

Affected product: Next4Biz CRM & BPM Software Business Process Manangement (BPM). 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-5683/ (Markdown: https://insights.sbomify.com/CVE-2024-5683/index.md)
```

## Sources

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

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