# CVE-2024-9150: Code Injection in Wyn Enterprise

> Attackers with low privileges can execute malicious code and OS commands via report generation, leading to high-privilege system compromise.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Feb 2025
- **Updated:** 21 Feb 2025
- **Also known as:** GHSA-qf7q-96xw-2xgh

## What is CVE-2024-9150?

CVE-2024-9150 is a high-severity code injection vulnerability in Wyn Enterprise, published on 21 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Report generation functionality in Wyn Enterprise allows for code inclusion, but not sufficiently limits what code might be included. An attacker is able use a low privileges account in order to abuse this functionality and execute malicious code, load DLL libraries and executing OS commands on a host system with applications high privileges.
This issue has been fixed in version 8.0.00204.0

Weakness: CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine)

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


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

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

## Is CVE-2024-9150 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-9150 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-9150 is a high-severity code injection vulnerability in Wyn Enterprise, published on 21 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-9150 exists.

Affected product: Wyn Enterprise. 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-9150/ (Markdown: https://insights.sbomify.com/CVE-2024-9150/index.md)
```

## Sources

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

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