# CVE-2022-41158: eyoom builder Remote Code Execution Vulnerability

> Remote attackers can execute arbitrary code by manipulating cookie values used as file paths in eyoom builder.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Nov 2022
- **Updated:** 29 Apr 2025
- **Also known as:** GHSA-qj9h-vqcc-rfjq

## What is CVE-2022-41158?

CVE-2022-41158 is a high-severity code injection vulnerability in eyoom builder, published on 25 Nov 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Remote code execution vulnerability can be achieved by using cookie values as paths to a file by this builder program. A remote attacker could exploit the vulnerability to execute or inject malicious code.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2022-41158?

It affects 1 product.


Products: Eyoom Eyoom Builder.

## How do I fix CVE-2022-41158?

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

## Is CVE-2022-41158 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-41158 and fix it if it is affected.

What it is: CVE-2022-41158 is a high-severity code injection vulnerability in eyoom builder, published on 25 Nov 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-41158 in the wild and no public exploit code.

Affected product: eyoom builder. 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-2022-41158/ (Markdown: https://insights.sbomify.com/CVE-2022-41158/index.md)
```

## Sources

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

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