# CVE-2022-28113: Auth bypass in n/a

> Attackers can bypass authentication to write files and reset user passwords on FANTEC MWiD25-DS devices without a valid session cookie.

- **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:** 15 Apr 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-3r85-3gpw-c7mc

## What is CVE-2022-28113?

CVE-2022-28113 is a high-severity authentication bypass vulnerability in n/a, published on 15 Apr 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An issue in upload.csp of FANTEC GmbH MWiD25-DS Firmware v2.000.030 allows attackers to write files and reset the user passwords without having a valid session cookie.

Weakness: CWE-565 (Reliance on Cookies without Validation and Integrity Checking)

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

It affects 1 product.


Products: Fantec Mwid25-Ds Firmware.

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

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

## Is CVE-2022-28113 being exploited?

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

Public exploit code:

- Unauthenticated RCE exploit for Fantec MWiD25-DS (github_poc): https://github.com/code-byter/CVE-2022-28113

## Other vulnerabilities in n/a

- [CVE-2022-26591](https://insights.sbomify.com/CVE-2022-26591/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-28113 is a high-severity authentication bypass vulnerability in n/a, published on 15 Apr 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-28113 in the wild and no public exploit code.

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

## Sources

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

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