# CVE-2022-41157: ERP solution Remote Code Execution Vulnerability

> Attackers can exploit a fixed password with SYSTEM authority to execute malicious commands and steal sensitive information in the sERP server.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/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:** 25 Nov 2022
- **Updated:** 24 Apr 2025
- **Also known as:** GHSA-65h8-8v7v-fpc7

## What is CVE-2022-41157?

CVE-2022-41157 is a high-severity vulnerability in Webcash Co.,Ltd sERP Server 2.0, published on 25 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A specific file on the sERP server if Kyungrinara(ERP solution) has a fixed password with the SYSTEM authority. This vulnerability could allow attackers to leak or steal sensitive information or execute malicious commands.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 1 product.


Products: Webcash Serp Server 2.0.

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

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

## Is CVE-2022-41157 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-41157 is a high-severity vulnerability in Webcash Co.,Ltd sERP Server 2.0, published on 25 Nov 2022. 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-2022-41157 in the wild and no public exploit code.

Affected product: Webcash Co.,Ltd sERP Server 2.0. 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-41157/ (Markdown: https://insights.sbomify.com/CVE-2022-41157/index.md)
```

## Sources

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

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