# CVE-2024-6917: RCE in Veribilim Software's Veribase Order Management

> Attackers can execute arbitrary OS commands via improper neutralization in Veribase Order Management, requiring an upgrade to secure the system.

- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2024
- **Updated:** 3 Jun 2026
- **Also known as:** GHSA-hq7f-8578-2f59

## What is CVE-2024-6917?

CVE-2024-6917 is a critical command injection vulnerability in Veribilim Software Veribase Order Management, published on 12 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in Veribilim Software Veribase Order Management allows OS Command Injection.

This issue affects Veribase Order Management: before v4.010.2.

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

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

It affects 1 product.


Products: Veribase Order Management.

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

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

## Is CVE-2024-6917 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-6917 is a critical command injection vulnerability in Veribilim Software Veribase Order Management, published on 12 Aug 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-6917 in the wild and no public exploit code.

Affected product: Veribilim Software Veribase Order Management. 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-6917/ (Markdown: https://insights.sbomify.com/CVE-2024-6917/index.md)
```

## Sources

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

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